Personalized plan development

ABSTRACT

A computationally implemented method includes, but is not limited to: receiving a request for a personalized plan designed to facilitate an end user to achieve one or more target outcomes when one or more emulatable aspects indicated by the personalized plan are emulated, the request identifying at least a source user; acquiring source user data indicating a plurality of reported aspects associated with at least the source user in response to receiving the request; and developing the personalized plan by at least determining which of the plurality of reported aspects associated with the source user are relevant to the achievement of the one or more target outcomes. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.

SUMMARY

A computationally implemented method includes, but is not limited toreceiving a request for a personalized plan designed to facilitate anend user to achieve one or more target outcomes when one or moreemulatable aspects indicated by the personalized plan are emulated, therequest identifying at least a source user; acquiring source user dataindicating a plurality of reported aspects associated with at least thesource user in response to receiving the request; and developing thepersonalized plan by at least determining which of the plurality ofreported aspects associated with the source user are relevant to theachievement of the one or more target outcomes. In addition to theforegoing, other method aspects are described in the claims, drawings,and text forming a part of the present disclosure.

In one or more various aspects, related systems include but are notlimited to circuitry and/or programming for effecting theherein-referenced method aspects; the circuitry and/or programming canbe virtually any combination of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

A computationally implemented system includes, but is not limited to:means for receiving a request for a personalized plan designed tofacilitate an end user to achieve one or more target outcomes when oneor more emulatable aspects indicated by the personalized plan areemulated, the request identifying at least a source user; means foracquiring source user data indicating a plurality of reported aspectsassociated with at least the source user in response to receiving therequest; and means for developing the personalized plan by at leastdetermining which of the plurality of reported aspects associated withthe source user are relevant to the achievement of the one or moretarget outcomes. In addition to the foregoing, other system aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

A computationally implemented system includes, but is not limited to:circuitry for receiving a request for a personalized plan designed tofacilitate an end user to achieve one or more target outcomes when oneor more emulatable aspects indicated by the personalized plan areemulated, the request identifying at least a source user; circuitry foracquiring source user data indicating a plurality of reported aspectsassociated with at least the source user in response to receiving therequest and circuitry for developing the personalized plan by at leastdetermining which of the plurality of reported aspects associated withthe source user are relevant to the achievement of the one or moretarget outcomes. In addition to the foregoing, other system aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

A computer program product including a signal-bearing medium bearing oneor more instructions for receiving a request for a personalized plandesigned to facilitate an end user to achieve one or more targetoutcomes when one or more emulatable aspects indicated by thepersonalized plan are emulated, the request identifying at least asource user; one or more instructions for acquiring source user dataindicating a plurality of reported aspects associated with at least thesource user in response to receiving the request; and one or moreinstructions for developing the personalized plan by at leastdetermining which of the plurality of reported aspects associated withthe source user are relevant to the achievement of the one or moretarget outcomes. In addition to the foregoing, other computer programproduct aspects are described in the claims, drawings, and text forminga part of the present disclosure.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE FIGURES

FIGS. 1 a and 1 b show a high-level block diagram of a server 10operating in a network environment.

FIGS. 1 c and 1 d show a high-level block diagram of a local source userdevice 20′ operating in a network environment.

FIGS. 1 e and 1 f show a high-level block diagram of a local end userdevice 30″ operating in a network environment.

FIG. 2 shows another perspective of the personalized plan developmentmodule 106* of the server 10 of FIG. 1 b, of the local source userdevice 20′ of FIG. 1 d, and of the local end user device 30″ of FIG. 1f.

FIG. 3 is a high-level logic flowchart of a process.

FIG. 4 a is a high-level logic flowchart of a process depictingalternate implementations of the reception operation 302 of FIG. 3.

FIG. 4 b is a high-level logic flowchart of a process depictingalternate implementations of the reception operation 302 of FIG. 3.

FIG. 4 c is a high-level logic flowchart of a process depictingalternate implementations of the reception operation 302 of FIG. 3.

FIG. 4 d is a high-level logic flowchart of a process depictingalternate implementations of the reception operation 302 of FIG. 3.

FIG. 4 e is a high-level logic flowchart of a process depictingalternate implementations of the reception operation 302 of FIG. 3.

FIG. 5 a is a high-level logic flowchart of a process depictingalternate implementations of the acquisition operation 304 of FIG. 3.

FIG. 5 b is a high-level logic flowchart of a process depictingalternate implementations of the acquisition operation 304 of FIG. 3.

FIG. 5 c is a high-level logic flowchart of a process depictingalternate implementations of the acquisition operation 304 of FIG. 3.

FIG. 5 d is a high-level logic flowchart of a process depictingalternate implementations of the acquisition operation 304 of FIG. 3.

FIG. 5 e is a high-level logic flowchart of a process depictingalternate implementations of the acquisition operation 304 of FIG. 3.

FIG. 5 f is a high-level logic flowchart of a process depictingalternate implementations of the acquisition operation 304 of FIG. 3.

FIG. 6 a is a high-level logic flowchart of a process depictingalternate implementations of the development operation 306 of FIG. 3.

FIG. 6 b is a high-level logic flowchart of a process depictingalternate implementations of the development operation 306 of FIG. 3.

FIG. 6 c is a high-level logic flowchart of a process depictingalternate implementations of the development operation 306 of FIG. 3.

FIG. 6 d is a high-level logic flowchart of a process depictingalternate implementations of the development operation 306 of FIG. 3.

FIG. 7 is a high-level logic flowchart of another process.

FIG. 8 is a high-level logic flowchart of a process depicting alternateimplementations of the presentation operation 708 of FIG. 7.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

A recent trend that has enjoyed explosive popularity in thecomputing/communication field is to electronically record one's dailyactivities, behaviors, thoughts, beliefs, traits, physical or mentalstates, physical characteristics, and other aspects of the person'severyday life onto an open diary. One place where such open diaries aremaintained is at social networking sites commonly known as “blogs” whereone or more users may report or post every aspect of their lives. Theprocess of reporting or posting blog entries is commonly referred to asblogging. Newer types of blogs that are also becoming increasinglypopular are known as microblogging or “twittering,” whereby each of themicroblogs that are posted are typically relatively short posts orentries, usually not more than 140 characters long.

Other social networking sites may allow users to update their personalinformation via, for example, social networking status reports in whicha user may report or post for others to view the latest status or otheraspects of the user. Although a wealth of personal information in theform of, for example, log data are now available through such socialnetworking sites, it is only recently has there been any effort toexploit such useful data.

In particular embodiments, robust methods, systems, circuitry, andcomputer program products are provided that may facilitate in thedevelopment of a plan that when executed by, for example, an end usermay result in the achievement of one or more target outcomes. In orderto develop the plan, a model (e.g., a source user), who may beassociated with the one or more outcomes, may be initially identified.The plan may then be developed by at least determining from a pluralityof reported events or aspects associated with the model those reportedaspects that may be relevant to the achievement of the one or moretarget outcomes. In some cases, the plurality of reported aspects may beindicated by, for example, log data such as data that may have been atleast originally acquired through social networking entries (e.g.,microblog entries and/or status reports), diary entries, and/or sensorreadings.

More generally, and in accordance with various embodiments, the robustmethods, systems, circuitry, and computer program products mayfacilitate in the development of a personalized plan designed to assistan end user in achieving one or more target outcomes when one or moreemulatable aspects indicated by the personalized plan are emulated. Insome implementations, a personalized plan may merely indicate acollection of one or more “emulatable aspects.” An emulatable aspect maybe any behavior, act, trait, physical state, mental state, social state,declaration, belief, or any other facet that may be emulated in order toachieve one or more target outcomes. In cases where the personalizedplan includes multiple emulatable aspects, the personalized plan may ormay not define a relationship or relationships (e.g., temporal, specifictime, or spatial relationships) between the emulatable aspects.

A target outcome may be any type of goal or desired result that may besought by an end user or by a third party. Examples of target outcomesinclude, for example, health-related outcomes such as weight loss orimproved cardiovascular conditioning, athletic outcomes such asdeveloping a particular athletic skill including being able to pitch acurve ball or achieving a particular golf handicap, physiologicaloutcomes such as reduced blood pressure or blood glucose levels, socialoutcomes such as obtaining membership into an elite social club orattaining a particular social status, mental state outcomes such asachieving certain level of calmness or happiness, interpersonal orrelational outcomes such as having lots of friends or developing skillto make friends, employment outcomes such as being promoted ordeveloping certain work skills, and so forth.

In various implementations, the robust methods, systems, circuitry, andcomputer program products may begin developing the personalized planwhen a request for the personalized plan designed to achieve the one ormore target outcomes is initially received. Such a request may at leastidentify a source user who may be the model for achieving the one ormore target outcomes. In other words, the source user may at least beperceived by, for example, an end user as having achieved the at leastone or more target outcomes. In some cases, the source user may be anactual or “real” person. While in other cases, the source user may be a“fictional” person (e.g., an alter ego created by someone's imagination)that is associated with the one or more target outcomes. In still othercases, a source user may be a composite person created from dataprovided by a plurality of “real” persons.

In some cases where the source user is an actual or “real” person, theend user may have become aware of the source user when the end useraccidently or randomly encountered the source user at some locale suchas the gym, at school, at the doctor's office, on the street, or at someother locale. Upon encountering the source user, the end user mayperceive that the source user is associated with some admirable quality(e.g., target outcome) and would like to have such a quality. For thesecases, the end user may obtain the identity of the source user by avariety of alternative means. For instance, in situations where the enduser randomly encounters the source user, the identity of the sourceuser may be obtained by using some sort of sensing device that may beemployed to unobtrusively acquire the identity of the source user.Example of such devices include, for example, a radio frequencyidentification (RFID) reader device (e.g., source user may carry anRFID), a facial recognition device, a device that determine thegeographical location of a source user such as certain types of cellulartelephones, and so forth.

Alternatively, a source user (e.g., actual, composite, or fictionalperson) may be listed at a website such as a social networking site.Such a website may allow an end user to access the identity of thesource user as well as provide indications of one or more desirablequalities (e.g., target outcomes) associated with the source user.

In any event, in response to receiving the request for the personalizedplan, “source user data” indicating one or more reported aspectsassociated with source user may be acquired (e.g., retrieved). In someimplementations, the acquired source user data may be in the form of logdata associated with the source user that may have been originally beenobtained via social networking entries such as microblog entries orstatus reports, via diary entries, and/or via data entries provided byone or more sensors. Alternatively, such source user data may at leastbe partially fictional or fabricated.

After acquiring the source user data, the methods, systems, circuitry,and computer program products may develop the personalized plan by atleast determining which of the one or more reported aspects associatedwith the source user and indicated by the source user data may berelevant to the achievement of the one or more target outcomes. Afterdetermining those reported aspects that are relevant to the achievementof the one or more target outcomes, the personalized plan may bedeveloped by including into the personalized plan one or more emulatableaspects that corresponds to one or more identified reported aspects thatare relevant to the achievement of the one or more target outcomes. Incertain implementations, where the personalized plan includes aplurality of emulatable aspects, the personalized plan may define therelationships (e.g., temporal, specific time, and/or spatialrelationships) between the emulatable aspects.

Turning now to FIGS. 1 a, 1 b, 1 c, 1 d, 1 e, and 1 f, illustratingthree example environments in which the methods, systems, circuitry, andcomputer program products in accordance with various embodiments may beimplemented by a computing device such as a server or a local userdevice. In particular, FIGS. 1 a and 1 b illustrates a first exampleenvironment in which the methods, systems, circuitry, and computerprogram products in accordance with some embodiments may be implementedat a server 10. FIGS. 1 c and 1 d illustrates a second exampleenvironment in which the methods, systems, circuitry, and computerprogram products in accordance with some embodiments may be implementedat a local source user device 20′. FIGS. 1 e and 1 f illustrate a thirdexample environment in which the methods, systems, circuitry, andcomputer program products in accordance with some embodiments may beimplemented at a local end user device 30″. Note that in the following,“*” represents a wildcard. Thus, “server 10*” in the followingdescription may be in reference to server 10 of the first exampleenvironment of FIGS. 1 a and 1 b, to server 10′ of the second exampleenvironment of FIGS. 1 c and 1 d, or to server 10″ of the third exampleenvironment of FIGS. 1 e and 1 f.

In various embodiments, the server 10 of FIG. 1 b, the local source userdevice 20′ of FIG. 1 d, and the local end user device 30″ of FIG. 1 fmay be designed to, among other things, receive a request 12* for apersonalized plan 16* that is designed to facilitate an end user 4* toachieve one or more target outcomes when one or more emulatable aspectsindicated by the personalized plan 16* are emulated, the request 12*identifying at least a source user 2*. In response to the receiving therequest 12*, the server 10, the local source user device 20′, and thelocal end user device 30″ may be designed to acquire source user data14* that may indicate a plurality of reported aspects associated withthe source user 2*.

After acquiring the source user data 14*, the server 10, the localsource user device 20′, and the local end user device 30″ may bedesigned to develop the personalized plan 16* by at least determiningwhich of the plurality of reported aspects associated with the sourceuser 2*are relevant to the achievement of the one or more targetoutcomes. In some implementations, the server 10, the local source userdevice 20′, and the local end user device 30″ may be further designed topresent the resulting personalized plan 16*.

Referring particularly now to FIGS. 1 a and 1 b illustrated the firstexample environment in accordance with various embodiments. Included inthe illustrated first environment of FIGS. 1 a and 1 b is a firstexemplary system 100, which includes at least a server 10 (see FIG. 1 b)that may be designed to communicate with at least a source user 2 (via alocal source user device 20) and an end user 4 (via a local end userdevice 30) through a wireless network and/or wired network 50. In someimplementations, the server 10 may further communicate with, via thewireless network and/or wired network 50, one or more third parties 6such as one or more other source users, one or more other end users, oneor more content providers, one or more network service providers, and/orone or more other third parties. The server 10 may also communicatewith, via the wireless network and/or wired network 50, one or moresensors 40.

In various implementations, the server 10 of FIG. 1 b (as well as theserver 10′ of FIG. 1 c and the server 10″ of FIG. 1 e) may be a networkserver that is designed to interface with a wireless network and/orwired network 50*. A network server, as will be described herein, may bein reference to a server located at a single network site or locatedacross multiple network sites or a conglomeration of servers located atmultiple network sites.

The local source user device 20 (as well as the local source user device20′ of FIG. 1 d and the local source user device 20″ of FIG. 1 e) andthe local end user device 30 (as well as the local end user device 30′of FIG. 1 c and the local end user device 30″ of FIG. 1 f) may be avariety of computing/computing devices including, for example, acellular phone, a personal digital assistant (PDA), a laptop, a desktop,or other types of computing/communication devices that can communicatewith the computing device 10. In some embodiments, the local source userdevice 20 (as well as the local source user device 20′ of FIG. 1 d andthe local source user device 20″ of FIG. 1 e) and/or the local end userdevice 30 (as well as the local end user device 30′ of FIG. 1 c and thelocal end user device 30″ of FIG. 1 f) may be a handheld device such asa cellular telephone, a smartphone, a Mobile Internet Device (MID), anUltra Mobile Personal Computer (UMPC), a convergent device such as apersonal digital assistant (PDA), and so forth.

In various embodiments, the one or more sensors 40 (as well as the oneor more sensors 40′ of FIG. 1 c and the one or more sensors 40″ of FIG.1 e) a wide range of devices that can monitor various aspects or eventsassociated with a source user 2*. For example, in some implementations,the one or more sensors 40* may include devices that can monitor auser's physiological characteristics such as blood pressure sensors,heart rate monitors, glucometers, and so forth. In some implementations,the one or more sensors 40* may include devices that can monitoractivities of a user (e.g., source user 2*) such as a pedometer, atoilet monitoring system (e.g., to monitor bowel movements), exercisemachine sensors, an accelerometer to measure a person's movements whichmay indicate specific activities, and so forth. The one or more sensors40* may also include other types of sensor/monitoring devices such asvideo or digital camera, global positioning system (GPS) to provide datathat may be related to a user (e.g., locations of the source user 2*),and so forth.

Referring back to the first exemplary environment of FIGS. 1 a and 1 b,the server 10 may receive a request 12 for a personalized plan 16 fromthe end user 4 via the local end user device 30. The request 12 mayidentify at least a source user 2. The requested personalized plan 16may be designed to facilitate the end user 4 to achieve one or moretarget outcomes when one or more emulatable aspects indicated by thepersonalized plan 16 are emulated. In response to receiving the request12, the server 10 may acquire source user data 14 that may indicate aplurality of reported aspects associated with at least the source user2. The source user data 14 may be acquired from a variety of sources.For example, in some implementations, at least a portion of the sourceuser data 14 may be acquired from a memory 116. In some implementations,at least a portion of the source user data 14 may be acquired from thelocal source user device 20. In some implementations, at least a portionof the source user data 14 may be acquired from the one or more thirdparties. In some implementations, at least a portion of the source userdata 14 may be acquired from one or more sensors 40.

After acquiring the source user data 14, the server 10 may develop thepersonalized plan 16 by at least determining which of the plurality ofreported aspects associated with the source user 2 are relevant to theachievement of the one or more target outcomes. In some implementations,the server 10 may then present the developed personalized plan 16 to theend user 4 (via the local end user device 30) and/or to one or morethird parties 6.

The server 10 as illustrated in FIG. 1 b may include a variety ofmodules, sub-modules, and components. As shown, the server 10 mayinclude a request reception module 102 (which may further include anetwork interface reception module 202, a source user data acquisitionmodule 104 (which may further include a request transmission module 204and/or source user data reception module 206), a personalized plandevelopment module 106, a presentation module 108 (which may furtherinclude a transmission module 228), a memory 116 (which may store sourceuser data 14 and/or one or more applications 140), and/or a networkinterface 118 (e.g., a network interface card or NIC). The server 10, invarious implementations, may further include a social networking entryreception module 110 (which may further include a blog entry receptionmodule 111 and/or status report reception module 112), a diary entryreception module 114, and/or a sensor data reception module 115.

The request reception module 102 may be configured to, among otherthings, receive a request 12 for a personalized plan 16 that is designedto facilitate an end user 4 to achieve one or more target outcomes whenone or more emulatable aspects indicated by the personalized plan 16 areemulated. The request 12 to be received by the request reception module102 may at least identify a source user 2. In some implementations, therequest 12 to be received by the request reception module 102 mayfurther include information that may facilitate in the development ofthe personalized plan 16 as will be further described herein. In orderto facilitate reception of a request 12 from, for example, a networkdevice (e.g., local end user device 30 or another server), the requestreception module 102 may include a network interface reception module202 designed to receive the request 12 via a wireless network and/orwired network 50.

The source user data acquisition module 104 may be configured toacquire, in response to the request reception module 102 receiving therequest 12, source user data 14 indicating a plurality of reportedaspects associated with at least the source user 2. In variousimplementations, the source user data acquisition module 104 may furtherinclude a request transmission module 204 designed to transmit (e.g.,via the wireless network and/or wired network 50) a request for thesource user data 14, and a source user data reception module 206designed to receive the source user data 14. The source user data 14acquired by the source user data acquisition module 104 may indicate, invarious implementations, at least a first one or more reported aspectsthat may be relevant to the achievement of the one or more targetoutcomes of the personalized plan 16, and a second one or more reportedaspects that may not be relevant to the achievement of the one or moretarget outcomes.

The personalized plan development module 106 may be configured to, amongother things, develop a personalized plan 16 by at least determiningwhich of the plurality of reported aspects associated with the sourceuser 2 as indicated by the source user data 14 are relevant to theachievement of the one or more target outcomes of the personalized plan16. For example, filtering the source user data 14 to determine ordistinguish those reported aspects (e.g., first one or more reportedaspects) that are relevant to the achievement of the one or more targetoutcomes from those reported aspects (e.g., second one or more reportedaspects) that are not relevant to the achievement of the one or moretarget outcomes. After determining which of the reported aspectsassociated with the source user 2 are relevant to the achievement of theone or more target outcomes, the personalized plan development module106 may develop the personalized plan 16 by including into thepersonalized plan 16 one or more emulatable aspects that corresponds toone or more reported aspects that have been determined to be relevant tothe achievement of the one or more target outcomes. As will be furtherdescribed herein, the personalized plan development module 106 invarious implementations may further include one or more sub-modules aswill be further described herein and as illustrated in FIG. 2.

The presentation module 108 may be configured to present thepersonalized plan 16 developed by the personalized plan developmentmodule 106 to the end user 4, the source user 2, and/or one or morethird parties 6. In some implementations, presentation module 108 mayfurther include a transmission module 228 that is configured to transmitthe personalized plan 16 via, for example, the wireless network and/orwired network 50.

A more detailed discussion relating to the request reception module 102,the source user data acquisition module 104, the personalized plandevelopment module 106, the presentation module 108, and theirsub-modules, will be provided below with respect to the variousoperational flows to be described herein. The social networking entryreception module 110 may be configured to receive social networkingentries from various sources including, for example, the source user 2,the end user 4, and/or one or more third parties 6. The socialnetworking entry reception module 110 may further include a blog entryreception module 111 that is configured to receive blog or microblogentries and/or a status report reception module 112 configured toreceive status reports. Similarly, the diary entry reception module 114may be configured to receive diary entries from, for example, the sourceuser 2, the end user 4, and/or from one or more third parties 6.

The sensor data reception module 115 may be configured to receivesensing data from one or more sensors 40. The memory 116 may compriseone or more volatile and/or non-volatile devices that may be used tostore data. In various implementations, the memory 116 may include, forexample, a mass storage device, read-only memory (ROM), programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),cache memory such as random access memory (RAM), flash memory,synchronous random access memory (SRAM), dynamic random access memory(DRAM), and/or other memory devices. The one or more applications 140that may be included in the memory 116 may comprise of, for example, oneor more communication applications (e.g., text messaging application,instant messaging application, email application, voice recognitionsystem, and so forth), Web 1.0 application, and/or Web 2.0 applicationto facilitate in communicating via, for example, the World Wide Web.

Referring now to FIGS. 1 c and 1 d, which as previously indicated,illustrates a second example environment in which the methods, systems,circuitry, and computer program products in accordance with variousembodiments may be implemented at a local source user device 20′ ratherthan at a server 10′ as was the case in the first example environment ofFIGS. 1 a and 1 b. As illustrated, the second example environment ofFIGS. 1 c and 1 d is similar to the first example environment of FIGS. 1a and 1 b.

In general, the second example environment of FIGS. 1 c and 1 d mayinclude a second exemplary system 100′, which includes at least a localsource user device 20′ (see FIG. 1 d). In various implementations, thelocal source user device 20′ as was the case for server 10 of FIGS. 1 aand 1 b may be designed to receive a request 12′ for a personalized plan16′ designed to facilitate an end user 4′ to achieve one or more targetoutcomes via a wireless network and/or wired network 50′. In someimplementations, the request 12′ may be received from an end user 4′.Alternatively, and although not depicted, the request 12′ may bereceived from a server 10′ or from one or more third parties 6′. Notethat server 10 of the first example environment of FIGS. 1 a and 1 b mayalso receive the request 12 from other sources (e.g., another server orone or more third parties 6) other than from an end user 4.

In any event, in response to receiving the request 12′, the local sourceuser device 20′ may be designed to acquire source user data 14′indicating a plurality of reported aspects associated with a source user2′ from one or more sources including, for example, a memory 116′, aserver 10′, one or more sensors 40′, and/or one or more third parties6′. The source user data 14′ acquired by the local source user device20′ may indicate, in various implementations, at least a first one ormore reported aspects that may be relevant to the achievement of the oneor more target outcomes of the personalized plan 16′, and a second oneor more reported aspects that may not be relevant to the achievement ofthe one or more target outcomes. The local source user device 20′ may befurther designed to develop a personalized plan 16′ by at leastdetermining which of the reported aspects associated with the sourceuser 2′ may be relevant to the achievement of the one or more targetoutcomes. For example, the local source user device 20′ may be designedto filter the source user data 14′ to determine or distinguish thosereported aspects (e.g., first one or more reported aspects) that arerelevant to the achievement of the one or more target outcomes fromthose reported aspects (e.g., second one or more reported aspects) thatare not relevant to the achievement of the one or more target outcomes.In some implementations, the local source user device 20′ may be furtherdesigned to present the developed personalized plan 16′ to the end user4′, one or more third parties 6′, and/or a server 10′.

The local source user device 20′, as illustrated in FIG. 1 d, mayinclude the same or similar modules, sub-modules, and componentsincluded in the server 10 of FIG. 1 b. As illustrated, the local sourceuser device 20′ may include a request reception module 102′ (which mayfurther include a network interface reception module 202′, a source userdata acquisition module 104′ (which may further include a requesttransmission module 204′ and a source user data reception module 206′),a personalized plan development module 106′, a presentation module 108′(which may further include a transmission module 228′), a memory 116′(which may store source user data 14′ and/or one or more applications140′), and/or a network interface 118′, similar to the server 10 of FIG.1 b.

Also similar to server 10 of FIG. 1 b, the local source user device 20′may also include a social networking entry reception module 110′ (whichmay further include a blog entry reception module 111′ and/or a statusreport reception module 112′), a diary entry reception module 114′,and/or a sensor data reception module 115′. All of these modules,sub-modules, and components of the local source user device 20′ mayperform the same or similar functions as their counterparts that may beincluded in the server 10 of FIG. 1 b. In addition to these modules,sub-modules, and components, the local source user device 20′ mayinclude a user interface 120′ and a user interface indication module229′ (which may be included with the presentation module 108′). The userinterface indication module 229′ may be designed to indicate, forexample, the personalized plan 16′ via the user interface 120′. The userinterface 120′ may include one or more of, for example, a displaymonitor, a touchscreen, a keyboard, a keypad, a mouse, an audio systemincluding one or more speakers, a microphone, an image capturing devicesuch as a digital camera, and so forth.

Turning now to FIGS. 1 e and 1 f, which as previously indicated,illustrates a third example environment in which the methods, systems,circuitry, and computer program products in accordance with variousembodiments may be implemented at a local end user device 30″ ratherthan at a server 10″ or at a local source user device 20″ as was thecase in the first and second example environments of FIGS. 1 a and 1 band FIGS. 1 c and 1 d. The third example environment of FIGS. 1 e and 1f is similar to the first example environment of FIGS. 1 a and 1 b andthe second example environment of FIGS. 1 c and 1 d with few minordifferences. For example, in the third example environment, the localend user device 30″ may receive a request 12″ for a personalized plan16″ directly from an end user 4* via a user interface 120″ rather thanfrom the wireless network and/or wired network 50″ as was the case forthe server 10 of the first example environment of FIGS. 1 a and 1 b andas was the case for the local source user device 20′ of the secondexample environment of FIGS. 1 c and 1 d. However, and as with theserver 10 and the local source user device 20′ of FIGS. 1 b and 1 d, thelocal end user device 30″ may also alternatively receive a request 12″via the wireless network and/or wired network 50″ from other sourcessuch as from one or more third parties 6″ or from a server 10″.

As illustrated, the third example environment of FIGS. 1 e and 1 f mayinclude a third exemplary system 100″, which includes at least a localend user device 30″ (see FIG. 1 f). In general, the local end userdevice 30″ may be designed to receive a request 12″ for a personalizedplan 16″ for facilitating an end user 4″ in achieving one or more targetoutcomes. In some implementations, the request 12″ may be receiveddirectly from the end user 4″ via a user interface 120″. Alternatively,and although not depicted, the request 12″ may be received via wirelessnetwork and/or wired network 50″ from, for example, one or more thirdparties 6″ or from a server 10″.

In response to receiving the request 12″, the local end user device 30″may be designed to acquire source user data 14″ indicating a pluralityof reported aspects associated with a source user 2″ from one or moresources including, for example, a memory 116″, a server 10″, one or moresensors 40″, and/or one or more third parties 6″. The source user data14″ acquired by the local end user device 30″ may indicate, in variousimplementations, at least a first one or more reported aspects that maybe relevant to the achievement of the one or more target outcomes of thepersonalized plan 16″, and a second one or more reported aspects thatmay not be relevant to the achievement of the one or more targetoutcomes. The local end user device 30″ may be further designed todevelop a personalized plan 16″ by at least determining which of thereported aspects associated with the source user 2″ may be relevant tothe achievement of the one or more target outcomes. For example, thelocal end user device 30″ may be designed to filter the source user data14″ to determine or distinguish those reported aspects (e.g., first oneor more reported aspects) that are relevant to the achievement of theone or more target outcomes from those reported aspects (e.g., secondone or more reported aspects) that are not relevant to the achievementof the one or more target outcomes. In various implementations, thelocal end user device 30″ may be further designed to present thedeveloped personalized plan 16″ to the end user 4″ (e.g., via the userinterface 120″), to one or more third parties 6″ (e.g., via wirelessnetwork and/or wired network 50″), and/or to a server 10″ (e.g., viawireless network and/or wired network 50″).

In various implementations, the local end user device 30″ may includethe same or similar modules, sub-modules, and components included in thelocal source user device 20′ of FIG. 1 d. For example, the local enduser device 30″ may include a request reception module 102″, a sourceuser data acquisition module 104″ (which may further include a requesttransmission module 204″ and a source user data reception module 206″),a personalized plan development module 106″, a presentation module 108″(which may further include a transmission module 228″ and a userinterface indication module 229″), a memory 116″ (which may store sourceuser data 14″ and/or one or more applications 140″), a user interface120″, and/or a network interface 118″, similar to the local source userdevice 20′ of FIG. 1 d. Also similar to the local source user device 20′of FIG. 1 d, the local end user device 30″ may also include a socialnetworking entry reception module 110″ (which may further include a blogentry reception module 111″ and/or a status report reception module112″), a diary entry reception module 114″, and/or a sensor datareception module 115″. All of these modules, sub-modules, and componentsof the local end user device 30″ may perform the same or similarfunctions as their counterparts that may be included in the local sourceuser device 20′ of FIG. 1 d. In addition to these modules, sub-modules,and components, the local end user device 30″ may include a userinterface reception module 203″ (which may be included in the requestreception module 102″) for receiving the request 12″ via a userinterface 120″. The user interface 120″ may include one or more of, forexample, a display monitor, a touchscreen, a keyboard, a keypad, amouse, an audio system including one or more speakers, a microphone, animage capturing device such as a digital camera, and so forth.

FIG. 2 illustrates the personalized plan development module 106*(e.g.,personalized plan development module 106, personalized plan developmentmodule 106′, and personalized plan development module 106″) of FIGS. 1b, 1 d, and 1 f. As illustrated, the personalized plan developmentmodule 106* may include a relevant reported aspect determination module208* that is configured to, among other things, determine which of aplurality of reported aspects associated with a source user 2*, asindicated by source user data 14*, are relevant to the achievement ofone or more target outcomes of a personalized plan 16*. In variousimplementations, the relevant reported aspect determination module 208*may be further configured to, among other things, determine which of theplurality of the reported aspects, as indicated by the source user data14*, occurred within a predefined time period from occurrence of one ormore reported outcomes associated with the source user 2* thatcorresponds to the one or more target outcomes of the personalized plan16*. In the same or different implementations, the relevant reportedaspect determination module 208* may be configured to determine which ofthe reported aspects as indicated by the source user data 14* arerelevant to the achievement of the one or more target outcomes based, atleast in part, on indications provided by the source user 2*, by the enduser 4*, and/or by one or more third party sources.

The relevant reported aspect determination module 208* may furtherinclude one or more sub-modules in various alternative implementations.For example, in various implementations, the relevant reported aspectdetermination module 208* may include one or more of a reported aspectrelevancy requesting module 212*, a reported aspect non-relevancyrequesting module 214*, an aspect type relevancy requesting module 216*,an aspect type non-relevancy requesting module 218*, a relevancyreception module 220*, and/or a non-relevancy reception module 221*. Inbrief, the reported aspect relevancy requesting module 212* may beconfigured to, among other things, request the source user 2* or the enduser 4* to provide one or more indications of which of the reportedaspects (as indicated by the source user data 14*) are relevant to theachievement of one or more reported outcomes (as may be indicated by thesource user data 14*) that corresponds to the one or more targetoutcomes of the personalized plan 16*.

In contrast, the reported aspect non-relevancy requesting module 214 maybe configured to, among other things, request the source user 2* or theend user 4* to provide one or more indications of which of the reportedaspects (as indicated by source user data 14*) are not relevant to theachievement of one or more reported outcomes (as may be indicated by thesource user data 14*) that corresponds to the one or more targetoutcomes of the personalized plan 16*. The aspect type relevancyrequesting module 216* may be configured to, among other things, requestthe end user 4* or the source user 2* to provide one or more indicationsof what types of aspects are relevant to the achievement of the one ormore target outcomes of the personalized plan 16*. In contrast, theaspect type non-relevancy requesting module 218* may be configured to,among other things, request the end user 4* or the source user 2* toprovide one or more indications of what types of aspects are relevant tothe achievement of the one or more target outcomes of the personalizedplan 16*.

The relevancy reception module 220* may be configured to receive (e.g.,receive from a source user 2*, an end user 4*, or one or more thirdparties 6*) indications as to which reported aspects or which types ofreported aspects are relevant to the achievement of the one or moretarget outcomes of the personalized plan 16*. In contrast, thenon-relevancy reception module 221* may be configured to receive (e.g.,receive from a source user 2*, an end user 4*, or one or more thirdparties 6*) indications as to which reported aspects or which types ofreported aspects are not relevant to the achievement of the one or moretarget outcomes of the personalized plan 16*.

In various alternative implementations, the personalized plandevelopment module 106* may further include one or more of an emulatableaspect inclusion module 222*, an intermediate outcome inclusion module224*, a relationship defining module 226*, and/or a plausible emulatableaspect inclusion module 228*. The emulatable aspect inclusion module222* may be configured to, among other things, facilitate thedevelopment of the personalized plan 16* by including into thepersonalized plan 16 at least one emulatable aspect that corresponds toat least one reported aspect associated with the source user 2* that isdetermined to be relevant to the achievement of the one or more targetoutcomes of the personalized plan 16*. The intermediate outcomeinclusion module 224* may be configured to, among other things,facilitate the development of the personalized plan 16* by includinginto the personalized plan 16* at least one intermediate outcome thatcorresponds to one or more reported intermediate outcomes as indicatedby the source user data 14*. The relationship defining module 226* maybe configured to, among other things, facilitate the development of thepersonalized plan 16* by defining in the personalized plan 16* arelationship or relationships (e.g., temporal, specific time, or spatialrelationships) between a plurality of emulatable aspects that may beincluded in the personalized plan 16*. The plausible emulatable aspectinclusion module 228 may be configured to, among other things,facilitate the development of the personalized plan 16* by includinginto the personalized plan 16* at least one plausible emulatable aspect,the at least one plausible emulatable aspect being at least oneemulatable aspect that has been successfully emulated by one or moreother end users (e.g., one or more third parties 6*).

A more detailed discussion related to the server 10 of FIG. 1 b, thelocal source user device 20′ of FIG. 1 d, and the local end user device30″ of FIG. 1 f will now be provided with respect to the processes andoperations to be described herein.

FIG. 3 illustrates an operational flow 300 representing exampleoperations related to, among other things, development of a personalizedplan 16* designed to facilitate an end user 4* to achieve one or moretarget outcomes by at least determining which of a plurality of reportedaspects associated with a source user 2* are relevant to the achievementof the one or more target outcomes. In some embodiments, the operationalflow 300 may be executed by, for example, the server 10 of FIG. 1 b, thelocal source user device 20′ of FIG. 1 d, or the local end user device30″ of FIG. 1 f.

In FIG. 3 and in the following figures that include various examples ofoperational flows, discussions and explanations may be provided withrespect to the three exemplary environments described above asillustrated in FIGS. 1 a and 1 b, FIGS. 1 c and 1 d, and FIGS. 1 e and 1f, and/or with respect to other examples (e.g., as provided in FIG. 2)and contexts. However, it should be understood that the operationalflows may be executed in a number of other environments and contexts,and/or in modified versions of FIGS. 1 a to 1 f, and 2. Also, althoughthe various operational flows are presented in the sequence(s)illustrated, it should be understood that the various operations may beperformed in other orders than those which are illustrated, or may beperformed concurrently.

Further, in FIG. 3 and in following figures, various operations may bedepicted in a box-within-a-box manner. Such depictions may indicate thatan operation in an internal box may comprise an optional exampleembodiment of the operational step illustrated in one or more externalboxes. However, it should be understood that internal box operations maybe viewed as independent operations separate from any associatedexternal boxes and may be performed in any sequence with respect to allother illustrated operations, or may be performed concurrently.

In any event, after a start operation, the operational flow 300 may moveto a reception operation 302 for receiving a request for a personalizedplan designed to facilitate an end user to achieve one or more targetoutcomes when one or more emulatable aspects indicated by thepersonalized plan are emulated, the request identifying at least asource user. For instance, and as a illustration, the request receptionmodule 102*(e.g., the request reception module 102, the requestreception module 102′, or the request reception module 102″) of theserver 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d, orthe local end user device 30″ of FIG. 1 f receiving a request 12* (e.g.,via a wireless network and/or wired network 50* or via a user interface120*) for a personalized plan 16* designed to facilitate an end user 4*to achieve one or more target outcomes (e.g., weight loss, developmentor improvement of user skills such as work skills, athletic or gameskills, or social skills, developing or having particular subjectiveuser states such as well-rested and/or well-being, and so forth) whenone or more emulatable aspects (e.g., one or more behaviors, one or moreacts, one or more beliefs, one or more traits, and/or other types ofcharacteristics or traits) indicated by the personalized plan 16* areemulated, the request identifying at least a source user 2*. Note thatin various implementations the request 12* does not need to specify theone or more target outcomes associated with the requested personalizedplan 16*. Instead, the request 12* may merely identify a particularsource user 2*. The identification of the source user 2* in the request12* may be made by various means including, for example, by actual name(e.g., “John Doe”), by a user name (e.g., “jdoe”), by a facial image ofthe source user, by RFID identification, by voice identification, bylocation identification, by title identification, and so forth.

Operational flow 300 may also include an acquisition operation 304 foracquiring source user data indicating a plurality of reported aspectsassociated with at least the source user in response to receiving therequest. For instance, and as a illustration, the source user dataacquisition module 104* of the server 10 of FIG. 1 b, of the localsource user device 20′ of FIG. 1 d, or of the local end user device 30″of FIG. 1 f acquiring (e.g., acquiring from a memory 116* and/or from awireless network and/or wired network 50*) source user data 14*indicating a plurality of reported aspects (e.g., reported acts,behavior, beliefs, and so forth) associated with at least the sourceuser 2* in response to receiving the request 12*.

Finally, operational flow 300 may include a development operation 306for developing the personalized plan by at least determining which ofthe plurality of reported aspects associated with the source user arerelevant to the achievement of the one or more target outcomes. Forinstance, and as a illustration, the personalized plan developmentmodule 106* including the relevant reported aspect determination module208* of the server 10 of FIG. 1 b, of the local source user device 20′of FIG. 1 d, or of the local end user device 30″ of FIG. 1 f developing(e.g., creating) the personalized plan 16* by having the relevantreported aspect determination module 208* at least determining which ofthe plurality of reported aspects associated with the source user 2* arerelevant to the achievement of the one or more target outcomes.

In various implementations, the reception operation 302 of FIG. 3 may beperformed in various alternative ways as illustrated in FIGS. 4 a, 4 b,4 c, 4 d, and 4 e. For example, the request 12* received through thereception operation 302 may be received by various means depending upon,for example, whether the operation is being implemented at a server 10(e.g., as in the embodiment depicted in FIGS. 1 a and 1 b), at a localsource user device 20′ (e.g., as in the embodiment depicted in FIGS. 1 cand 1 d), or at a local end user device 30″ (e.g., as in the embodimentdepicted in FIGS. 1 e and 10. For example, in some implementations thereception operation 302 may include an operation 402 for receiving therequest via a user interface as depicted in FIG. 4 a. For instance, theuser interface reception module 203″ of the local end user device 30″receiving the request 12″ via a user interface 120″ (e.g., an audiosystem including a microphone, a keypad, a touchscreen, a mouse, and soforth).

In some alternative implementations, however, the reception operation302 may include an operation 403 for receiving the request via at leastone of a wireless network and a wired network as depicted in FIG. 4 a.For instance, the network interface reception module 202*(e.g., networkinterface reception module 202 or network interface reception module202′) of the server 10 of FIG. 1 b or the local source user device 20′of FIG. 1 d receiving the request 12*(e.g., request 12 or request 12′)via at least one of wireless network and a wired network 50*.

Various types of personalized plan 16* may be requested via thereception operation 302 of FIG. 3 in various alternativeimplementations. For example, in some implementations, the receptionoperation 302 may include an operation 404 for receiving a request for apersonalized plan designed to facilitate an end user to achieve one ormore outcomes related to athletics as depicted in FIG. 4 a. Forinstance, the request reception module 102* of the server 10 of FIG. 1b, the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f receiving a request 12* for a personalized plan16* designed to facilitate an end user 4* to achieve one or moreoutcomes related to athletics (e.g., an athletic skill or result such asbeing able to pitch a curve ball or running a mile under 6 minutes)when, for example, one or more emulatable aspects of the personalizedplan 16* are emulated. Note again that in various alternativeimplementations, the request 12* may not specifically identify the oneor more outcomes, but instead, may merely identify a source user 2*.

In some implementations, the reception operation 302 may include anoperation 405 for receiving a request for a personalized plan designedto facilitate an end user to achieve one or more outcomes relating togames as depicted in FIG. 4 a. For instance, the request receptionmodule 102* of the server 10 of FIG. 1 b, the local source user device20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1 f receivinga request 12* for a personalized plan 16* designed to facilitate an enduser 4* to achieve one or more outcomes related to games (e.g., a gamingskill or result relating to playing chess or a video/electronic game)when, for example, one or more emulatable aspects of the personalizedplan 16* are emulated.

In some implementations, the reception operation 302 may include anoperation 406 for receiving a request for a personalized plan designedto facilitate an end user to achieve one or more work related outcomesas depicted in FIG. 4 a. For instance, the request reception module 102*of the server 10 of FIG. 1 b, the local source user device 20′ of FIG. 1d, or the local end user device 30″ of FIG. 1 f receiving a request 12*for a personalized plan 16* designed to facilitate an end user 4* toachieve one or more work-related outcomes (e.g., obtaining a promotion,work related skills such as computer skills, interpersonal skills, andso forth) when, for example, one or more emulatable aspects of thepersonalized plan 16* are emulated.

In some implementations, the reception operation 302 may include anoperation 407 for receiving a request for a personalized plan designedto facilitate an end user to achieve one or more social related outcomesas depicted in FIG. 4 a. For instance, the request reception module 102*of the server 10 of FIG. 1 b, the local source user device 20′ of FIG. 1d, or the local end user device 30″ of FIG. 1 f receiving a request 12*for a personalized plan 16* designed to facilitate an end user 4* toachieve one or more social related outcomes (e.g., having many friends,participating in many social activities, interpersonal skills such aspublic speaking, and so forth) when, for example, one or more emulatableaspects of the personalized plan 16* are emulated.

In some implementations, the reception operation 302 may include anoperation 408 for receiving a request for a personalized plan designedto facilitate an end user to achieve one or more leisure relatedoutcomes as depicted in FIG. 4 a. For instance, the request receptionmodule 102* of the server 10 of FIG. 1 b, the local source user device20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1 f receivinga request 12* for a personalized plan 16* designed to facilitate an enduser 4* to achieve one or more leisure related outcomes (e.g., going ona vacation or being available to take a vacation, having or settingaside time to read a novel, and so forth) when, for example, one or moreemulatable aspects of the personalized plan 16* are emulated.

In some implementations, the reception operation 302 may include anoperation 409 for receiving a request for a personalized plan designedto facilitate an end user to achieve one or more health or medicalrelated outcomes as depicted in FIG. 4 a. For instance, the requestreception module 102* of the server 10 of FIG. 1 b, the local sourceuser device 20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1f receiving a request 12* for a personalized plan 16* designed tofacilitate an end user 4* to achieve one or more health or medicalrelated outcomes (e.g., reducing blood pressure or blood glucose levels,weight loss, increase red blood cell count, improve recovery from anillness such as cancer, and so forth) when, for example, one or moreemulatable aspects of the personalized plan 16* are emulated.

In some implementations, the reception operation 302 may include anoperation 410 for receiving a request for a personalized plan designedto facilitate an end user to achieve one or more sexual intimacyoutcomes as depicted in FIG. 4 a. For instance, the request receptionmodule 102* of the server 10 of FIG. 1 b, the local source user device20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1 f receivinga request 12* for a personalized plan 16* designed to facilitate an enduser 4* to achieve one or more sexual intimacy outcomes (e.g., increasedsexual activities, increased sexual performance, and so forth) when, forexample, one or more emulatable aspects of the personalized plan 16* areemulated.

In some implementations, the reception operation 302 may include anoperation 411 for receiving a request for a personalized plan designedto facilitate an end user to achieve one or more psychological relatedoutcomes as depicted in FIG. 4 b. For instance, the request receptionmodule 102* of the server 10 of FIG. 1 b, the local source user device20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1 f receivinga request 12* for a personalized plan 16* designed to facilitate an enduser 4* to achieve one or more psychological related outcomes (e.g.,easing of a phobia, hostile feeling towards a person or a group, and soforth) when, for example, one or more emulatable aspects of thepersonalized plan 16* are emulated.

In some implementations, the reception operation 302 may include anoperation 412 for receiving a request for a personalized plan designedto facilitate an end user to achieve one or more subjective user statesas depicted in FIG. 4 b. For instance, the request reception module 102*of the server 10 of FIG. 1 b, the local source user device 20′ of FIG. 1d, or the local end user device 30″ of FIG. 1 f receiving a request 12*for a personalized plan 16* designed to facilitate an end user 4* toachieve one or more subjective user states when, for example, one ormore emulatable aspects of the personalized plan 16* are emulated. Asubjective user state may be any user state that may generally only besubjectively indicated by a user. The requested personalized plan 16*may be designed to facilitate an end user 4* to achieve various types ofsubjective user states.

For example, in some implementations, operation 412 may further includean operation 413 for receiving a request for a personalized plandesigned to facilitate an end user to achieve one or more subjectiveuser mental states as depicted in FIG. 4 b. For instance, the requestreception module 102* of the server 10 of FIG. 1 b, the local sourceuser device 20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1f receiving a request 12* for a personalized plan 16* designed tofacilitate an end user 4* to achieve one or more subjective user mentalstates (e.g., happiness, calmness, alertness, and so forth) when, forexample, one or more emulatable aspects of the personalized plan 16* areemulated.

In some implementations, operation 412 may include an operation 414 forreceiving a request for a personalized plan designed to facilitate anend user to achieve one or more subjective user physical states asdepicted in FIG. 4 b. For instance, the request reception module 102* ofthe server 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d,or the local end user device 30″ of FIG. 1 f receiving a request 12* fora personalized plan 16* designed to facilitate an end user 4* to achieveone or more subjective user physical states (e.g., feeling energized,being pain-free, being able to see and/or hear well, and so forth) when,for example, one or more emulatable aspects of the personalized plan 16*are emulated.

In some implementations, operation 412 may include an operation 415 forreceiving a request for a personalized plan designed to facilitate anend user to achieve one or more subjective user overall states asdepicted in FIG. 4 b. For instance, the request reception module 102* ofthe server 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d,or the local end user device 30″ of FIG. 1 f receiving a request 12* fora personalized plan 16* designed to facilitate an end user 4* to achieveone or more subjective user overall states (e.g., “good,” “bad,” “well,”“available,” “busy,” and so forth) when, for example, one or moreemulatable aspects of the personalized plan 16* are emulated.

In some implementations, the reception operation 302 may include anoperation 416 for receiving a request for a personalized plan designedto facilitate an end user to achieve one or more user social states asdepicted in FIG. 4 b. For instance, the request reception module 102* ofthe server 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d,or the local end user device 30″ of FIG. 1 f receiving a request 12* fora personalized plan 16* designed to facilitate an end user 4* to achieveone or more social states (e.g., being available for marriage, belongingto a higher social class, and so forth) when, for example, one or moreemulatable aspects of the personalized plan 16* are emulated.

In some implementations, the reception operation 302 may include anoperation 417 for receiving a request for a personalized plan designedto facilitate an end user to achieve one or more user employment statesas depicted in FIG. 4 b. For instance, the request reception module 102*of the server 10 of FIG. 1 b, the local source user device 20′ of FIG. 1d, or the local end user device 30″ of FIG. 1 f receiving a request 12*for a personalized plan 16* designed to facilitate an end user 4* toachieve one or more user employment states (e.g., being employed, havingor obtaining an employment position such as a management position,having or developing a particular reputation at work, and so forth)when, for example, one or more emulatable aspects of the personalizedplan 16* are emulated.

In order to identify the source user 2*, in some implementations, therequest 12* received through the reception operation 302 of FIG. 3 mayinclude an identifier for the source user 2*. For example, in someimplementations, the reception operation 302 may include an operation418 for receiving the request for the personalized plan designed tofacilitate the end user to achieve the one or more target outcomes whenthe one or more emulatable aspects indicated by the personalized planare emulated, the request including an identifier associated with atleast the source user as depicted in FIG. 4 b. For instance, the requestreception module 102* of the server 10 of FIG. 1 b, the local sourceuser device 20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1f receiving the request 12* for the personalized plan 16* designed tofacilitate the end user 4* to achieve the one or more target outcomeswhen the one or more emulatable aspects indicated by the personalizedplan 16* are emulated, the request 12* including an identifier (e.g., an“actual” name, a user name, a title or position such as CEO oradministrative assistant, accomplishment such as “winner,” class such asprofessional football player, an image of the source user's face, anRFID identity, an avatar identity, voice recognition identification,retinal scan identification, digital fingerprint identification, creditcard, social security number, and so forth) associated with at least thesource user 2*.

In some cases, the request 12*received through the reception operation302 of FIG. 3 may identify at least one of the target outcomes of thepersonalized plan 16*. For example, in some implementations, thereception operation 302 may include an operation 419 for receiving therequest for the personalized plan designed to facilitate the end user toachieve the one or more target outcomes when the one or more emulatableaspects indicated by the personalized plan are emulated, the requestidentifying at least one of the one or more target outcomes as depictedin FIG. 4 c. For instance, the request reception module 102* of theserver 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d, orthe local end user device 30″ of FIG. 1 f receiving the request 12* forthe personalized plan 16* designed to facilitate the end user 4* toachieve one or more target outcomes when one or more emulatable aspectsindicated by the personalized plan 16* are emulated, the request 12*identifying at least one of the one or more target outcomes.

In some cases, operation 419 may further include an operation 420 forreceiving the request for the personalized plan designed to facilitatethe end user to achieve the one or more target outcomes when the one ormore emulatable aspects indicated by the personalized plan are emulated,the request including an identifier associated with at least one of theone or more target outcomes as depicted in FIG. 4 c. For instance, therequest reception module 102* of the server 10 of FIG. 1 b, the localsource user device 20′ of FIG. 1 d, or the local end user device 30″ ofFIG. 1 f receiving the request 12* for the personalized plan 16*designed to facilitate the end user 4* to achieve the one or more targetoutcomes when the one or more emulatable aspects indicated by thepersonalized plan 16* are emulated, the request 12* including anidentifier (e.g., a description, a name, a symbolic representation, animage of the outcome as physically displayed by, for example, the sourceuser 2* or a third party 6*, and so forth) associated with at least oneof the one or more target outcomes.

The request 12* received through the reception operation 302 of FIG. 3may indicate other types of information in various alternativeimplementations. For example, in some implementations, operation 302 mayinclude an operation 421 for receiving the request for the personalizedplan designed to facilitate the end user to achieve the one or moretarget outcomes when the one or more emulatable aspects indicated by thepersonalized plan are emulated, the request indicating one or morepreferences of the end user as depicted in FIG. 4 c. For instance, therequest reception module 102* of the server 10 of FIG. 1 b, the localsource user device 20′ of FIG. 1 d, or the local end user device 30″ ofFIG. 1 f receiving the request 12* for a personalized plan 16* designedto facilitate an end user 4* to achieve one or more target outcomes whenone or more emulatable aspects indicated by the personalized plan 16*are emulated, the request 12* indicating one or more preferences (e.g.,prefer not to jog, prefer not to wake-up early, prefer not to consumecertain items, and so forth) of the end user 4*.

In some implementations, the reception operation 302 may include anoperation 322 for receiving the request for the personalized plandesigned to facilitate the end user to achieve the one or more targetoutcomes when the one or more emulatable aspects indicated by thepersonalized plan are emulated, the request indicating one or morelimitations associated with the end user as depicted by FIG. 4 d. Forinstance, the request reception module 102* of the server 10 of FIG. 1b, the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f receiving the request 12* for a personalized plan16* designed to facilitate an end user 4* to achieve one or more targetoutcomes when one or more emulatable aspects indicated by thepersonalized plan 16* are emulated, the request 12* indicating one ormore limitations (e.g., physical or mental handicaps, schedulinglimitations, logistical limitations, and so forth) associated with theend user 4*.

Operation 422, in turn, may further include an operation 423 forreceiving the request for the personalized plan designed to facilitatethe end user to achieve the one or more target outcomes when the one ormore emulatable aspects indicated by the personalized plan are emulated,the request indicating one or more physical limitations associated withthe end user as depicted in FIG. 4 d. For instance, the requestreception module 102* of the server 10 of FIG. 1 b, the local sourceuser device 20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1f receiving the request 12* for a personalized plan 16* designed tofacilitate an end user 4* to achieve one or more target outcomes whenone or more emulatable aspects indicated by the personalized plan 16*are emulated, the request 12* indicating one or more physicallimitations (e.g., visual or hearing limitations, physical movementlimitations such as those related to a paraplegic, physicalcharacteristic limitations such as height, weight, and so forth, relatedto the end user 4*, physiological limitations such as cholesterollevels, and so forth) associated with the end user 4*.

In the same or different implementations, operation 422 may include anoperation 424 for receiving the request for the personalized plandesigned to facilitate the end user to achieve the one or more targetoutcomes when the one or more emulatable aspects indicated by thepersonalized plan are emulated, the request indicating one or morecontextual limitations associated with the end user as depicted in FIG.4 d. For instance, the request reception module 102* of the server 10(of FIG. 1 b), the local source user device 20′ (of FIG. 1 d), or thelocal end user device 30″ (of FIG. 1 f) receiving the request 12* for apersonalized plan 16* designed to facilitate an end user 4* to achieveone or more target outcomes when one or more emulatable aspectsindicated by the personalized plan 16* are emulated, the request 12*indicating one or more contextual limitations (e.g., schedulinglimitations, geographical limitations, asset limitations such as lack ofparticular equipment or facilities, and so forth) associated with theend user 4*.

In the same or different implementations, operation 422 may include anoperation 425 for receiving the request for the personalized plandesigned to facilitate the end user to achieve the one or more targetoutcomes when the one or more emulatable aspects indicated by thepersonalized plan are emulated, the request indicating one or morepersonal limitations associated with the end user as depicted in FIG. 4d. For instance, the request reception module 102* of the server 10 ofFIG. 1 b, the local source user device 20′ of FIG. 1 d, or the local enduser device 30″ of FIG. 1 f receiving the request 12* for a personalizedplan 16* designed to facilitate an end user 4* to achieve one or moretarget outcomes when one or more emulatable aspects indicated by thepersonalized plan 16* are emulated, the request 12* indicating one ormore personal limitations (e.g., religious beliefs, dietary beliefs,phobias, personal prejudices, limitations related to personalexperiences, personal work schedule, family dynamics or circumstances,and so forth) associated with the end user 4*.

In the same or different implementations, operation 422 may include anoperation 426 for receiving the request for the personalized plandesigned to facilitate the end user to achieve the one or more targetoutcomes when the one or more emulatable aspects indicated by thepersonalized plan are emulated, the request indicating one or moremedical or health limitations associated with the end user as depictedin FIG. 4 e. For instance, the request reception module 102* of theserver 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d, orthe local end user device 30″ of FIG. 1 f receiving the request 12* fora personalized plan 16* designed to facilitate an end user 4* to achieveone or more target outcomes when one or more emulatable aspectsindicated by the personalized plan 16* are emulated, the request 12*indicating one or more medical or health limitations (e.g., medicallimitations as limitations resulting from an illness or treatment of theillness including physical limitations due to cancer or treatmentthereof, health limitations related to the physical conditioning of theend user 4*, genetic limitations, and so forth) associated with the enduser 4*.

In the same or different implementations, operation 422 may include anoperation 427 for receiving the request for the personalized plandesigned to facilitate the end user to achieve the one or more targetoutcomes when the one or more emulatable aspects indicated by thepersonalized plan are emulated, the request indicating one or more userstate limitations associated with the end user as depicted in FIG. 4 e.For instance, the request reception module 102* of the server 10 of FIG.1 b, the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f receiving the request 12* for a personalized plan16* designed to facilitate an end user 4* to achieve one or more targetoutcomes when one or more emulatable aspects indicated by thepersonalized plan 16* are emulated, the request 12* indicating one ormore user state limitations (e.g., end user 4* is married, end user 4*is in mourning, end user 4* is unemployed, end user 4* is a vegan, andso forth) associated with the end user 4*.

In the same or different implementations, operation 422 may include anoperation 428 for receiving the request for the personalized plandesigned to facilitate the end user to achieve the one or more targetoutcomes when the one or more emulatable aspects indicated by thepersonalized plan are emulated, the request indicating one or more legalor regulatory limitations associated with the end user as depicted inFIG. 4 e. For instance, the request reception module 102* of the server10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or thelocal end user device 30″ of FIG. 1 f receiving the request 12* for apersonalized plan 16* designed to facilitate an end user 4* to achieveone or more target outcomes when one or more emulatable aspectsindicated by the personalized plan 16* are emulated, the request 12*indicating one or more legal or regulatory limitations (e.g., drugregulations, laws related to conduct, and so forth) associated with theend user 4*. Note that the legal or regulatory limitations between wherethe source user 2* resides and where the end user 4* resides may differ,and therefore, such information may be useful in developing apersonalized plan 16*.

Referring back to FIG. 3, the acquisition operation 304 may be executedin a variety of different manners in various alternativeimplementations. For instance, the source user data 14* acquired throughthe acquisition operation 304 may be acquired from different sourcesand/or may have at least originated from different sources. For example,in some implementations, the acquisition operation 304 may include anoperation 529 for acquiring at least a portion of the source user datafrom a remote network device as depicted in FIG. 5 a. For instance, thesource user data acquisition module 104* of the server 10 of FIG. 1 b,the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f acquiring at least a portion of the source userdata 14*(e.g., log data such as social networking entry data or diarydata) from a remote network device (e.g., in embodiments in whichoperational flow 300 is implemented at a server 10 as depicted in FIGS.1 a and 1 b, at least a portion of the source user data 14 may beacquired from a local source user device 20, from one or more thirdparty devices such as other source user devices, and/or from one or moresensors 40).

In some implementations, operation 529 may, in turn, include anoperation 530 for transmitting a request to the remote network devicefor the at least a portion of the source user data, the requestidentifying at least the source user as depicted in FIG. 5 a. Forinstance, the request transmission module 204* of the server 10 of FIG.1 b, the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f transmitting (e.g., via wireless network and/orwired network 50) a request to the remote network device for the atleast a portion of the source user data 14*, the request identifying atleast the source user 2*. For example, in embodiments in which theoperational flow 300 is being executed at a local end user device 30″(e.g., FIGS. 1 e and 10, the request transmission module 204″ of thelocal end user device 30″ may transmit to the server 10″, the localsource user device 20″, and/or one or more sensors 40″ a request for atleast a portion of the source user data 14″, the request identifying atleast the source user 2″. In various implementations, the source userdata reception module 206* of the server 10 of FIG. 1 b, the localsource user device 20′ of FIG. 1 d, or the local end user device 30″ ofFIG. 1 f may then receive the requested source user data 14*.

In the same or different implementations, operation 529 may include anoperation 531 for transmitting a request to the remote network devicefor the at least a portion of the source user data, the requestidentifying at least one of the one or more target outcomes as depictedin FIG. 5 a. For instance, the request transmission module 204* of theserver 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d, orthe local end user device 30″ of FIG. 1 f transmitting (e.g., viawireless network and/or wired network 50) a request to the remotenetwork device for the at least a portion of the source user data 14*,the request identifying at least one of the one or more target outcomes.For example, in embodiments in which the operational flow 300 is beingexecuted at a local source user device 20′ (e.g., FIGS. 1 c and 1 d),the request transmission module 204′ of the local source user device 20′may transmit to the server 10′ and/or one or more sensors 40′ a requestfor at least a portion of the source user data 14″, the requestidentifying at least one of the one or more target outcomes of thepersonalized plan 16′.

In some implementations, the acquisition operation 304 may include anoperation 532 for acquiring at least a portion of the source user datafrom a memory as depicted in FIG. 5 a. For instance, the source userdata acquisition module 104* of the server 10 of FIG. 1 b or the localsource user device 20′ of FIG. 1 d acquiring at least a portion of thesource user data 14* from a memory 116*(e.g., flash memory, volatilememory, non-volatile memory, cache memory, and so forth).

In some implementations, the acquisition operation 304 may include anoperation 533 for acquiring the source user data including dataindicating one or more reported aspects as at least originally reportedby the source user as depicted in FIG. 5 a. For instance, the sourceuser data acquisition module 104* of the server 10 of FIG. 1 b, thelocal source user device 20′ of FIG. 1 d, or the local end user device30″ of FIG. 1 f acquiring the source user data 14* including dataindicating one or more reported aspects as at least originally reportedby the source user 2*.

In some implementations, the acquisition operation 304 may include anoperation 534 for acquiring the source user data including dataindicating one or more reported aspects as at least originally reportedby one or more sensors as depicted in FIG. 5 a. For instance, the sourceuser data acquisition module 104* of the server 10 of FIG. 1 b, thelocal source user device 20′ of FIG. 1 d, or the local end user device30″ of FIG. 1 f acquiring the source user data 14* including dataindicating one or more reported aspects as at least originally reportedby one or more sensors 40*(e.g., physiological sensing devices such asblood pressure or blood glucose sensors, sensors to sense activities ofa subject such as pedometers, GPSs, exercise machine sensors, andaccelerometers, sensors to measure environmental conditions such asthermometers or air quality sensors, and so forth).

In some implementations, the acquisition operation 304 may include anoperation 535 for acquiring the source user data including dataindicating one or more reported aspects as at least originally reportedby one or more third parties as depicted in FIG. 5 a. For instance, thesource user data acquisition module 104* of the server 10 (of FIG. 1 b),the local source user device 20′ (of FIG. 1 d), or the local end userdevice 30″ (of FIG. 1 f) acquiring the source user data 14* includingdata indicating one or more reported aspects as at least originallyreported by one or more third parties 6*(e.g., other end users, spouses,friends, employers, and so forth).

In some implementations, the acquisition operation 304 may include anoperation 536 for acquiring the source user data including dataindicating one or more reported aspects as at least originally reportedvia one or more social networking entries as depicted in FIG. 5 b. Forinstance, the source user data acquisition module 104* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f acquiring the source user data 14*including data (e.g., log data) indicating one or more reported aspectsas at least originally reported via one or more social networkingentries.

In various implementations, operation 536 may further include anoperation 537 for acquiring the source user data including dataindicating one or more reported aspects as at least originally reportedvia one or more blog entries as depicted in FIG. 5 b. For instance, thesource user data acquisition module 104* of the server 10 of FIG. 1 b,the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f acquiring the source user data 14* including data(e.g., log data) indicating one or more reported aspects as at leastoriginally reported via one or more blog (e.g., microblog) entries(e.g., as entered by the source user 2* or by a third party 6*).

In some implementations, operation 536 may further include an operation538 for acquiring the source user data including data indicating one ormore reported aspects as at least originally reported via one or morestatus reports as depicted in FIG. 5 b. For instance, the source userdata acquisition module 104* of the server 10 of FIG. 1 b, the localsource user device 20′ of FIG. 1 d, or the local end user device 30″ ofFIG. 1 f acquiring the source user data 14* including data (e.g., logdata) indicating one or more reported aspects as at least originallyreported via one or more status reports (e.g., as reported by the sourceuser 2* or by a third party 6*).

In various implementations, the acquisition operation 304 may include anoperation 539 for acquiring the source user data including dataindicating one or more reported aspects as at least originally reportedvia one or more diary entries as depicted in FIG. 5 b. For instance, thesource user data acquisition module 104* of the server 10 of FIG. 1 b,the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f acquiring the source user data 14* including data(e.g., log data) indicating one or more reported aspects as at leastoriginally reported via one or more diary entries (e.g., as entered bythe source user 2* or by a third party 6*). Note that in some cases,diary entries may also include data provided by one or more sensors 40*.

In some implementations, the acquisition operation 304 may include anoperation 540 for acquiring the source user data including log dataindicating one or more reported factual aspects associated with at leastthe source user in response to receiving the request as depicted in FIG.5 b. For instance, the source user data acquisition module 104* of theserver 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d, orthe local end user device 30″ of FIG. 1 f acquiring the source user data14* including log data indicating one or more reported factual aspects(e.g., rather than fictional or imaginary aspects) associated with atleast the source user 2* in response to receiving the request 12*.

In some implementations, the acquisition operation 304 may include anoperation 541 for acquiring the source user data including dataindicating one or more reported fictional or fabricated aspectsassociated with at least the source user in response to receiving therequest as depicted in FIG. 5 b. For instance, the source user dataacquisition module 104* of the server 10 of FIG. 1 b, the local sourceuser device 20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1f acquiring the source user data 14* including data indicating one ormore reported fictional or fabricated aspects associated with at leastthe source user 2* in response to receiving the request 12*.

Various types of reported aspects associated with a source user 2* maybe indicated by the source user data 14* acquired through theacquisition operation 304 of FIG. 3. For example, in someimplementations, the acquisition operation 304 may include an operation542 for acquiring the source user data indicating the plurality ofreported aspects including one or more user behavior incidencesassociated with the source user as depicted in FIG. 5 c. For instance,the source user data acquisition module 104* of the server 10 of FIG. 1b, the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f acquiring the source user data 14* indicating theplurality of reported aspects including one or more user behaviorincidences (e.g., dietary behavior, exercise or athletic behavior,social behavior, work behavior, sexual behavior, and so forth)associated with the source user 2*.

Operation 542, in turn, may include one or more additional operations invarious alternative implementations. For example, in someimplementations, operation 542 may include an operation 543 foracquiring the source user data indicating the plurality of reportedaspects including one or more acts that were executed by the source useras depicted in FIG. 5 c. For instance, the source user data acquisitionmodule 104* of the server 10 of FIG. 1 b, the local source user device20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1 f acquiringthe source user data 14* indicating the plurality of reported aspectsincluding one or more acts (e.g., exercising, eating, driving, sleeping,waking-up early, reading, studying, and so forth) that were executed bythe source user 2*.

In the same or different implementations, operation 542 may include anoperation 544 for acquiring the source user data indicating theplurality of reported aspects including one or more incidences of userattitudes associated with the source user as depicted in FIG. 5 c. Forinstance, the source user data acquisition module 104* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f acquiring the source user data 14*indicating the plurality of reported aspects including one or moreincidences of user attitudes (e.g., anger, happiness, skeptical, alert,hostile, accepting, indifference, and so forth) associated with thesource user 2*.

In the same or different implementations, operation 542 may include anoperation 545 for acquiring the source user data indicating theplurality of reported aspects including one or more incidences of userconduct associated with the source user as depicted in FIG. 5 c. Forinstance, the source user data acquisition module 104* of the server 10(of FIG. 1 b), the local source user device 20′ (of FIG. 1 d), or thelocal end user device 30″ (of FIG. 10 acquiring the source user data 14*indicating the plurality of reported aspects including one or moreincidences of user conduct (e.g., how a source user 2* interacts withothers, how a source user 2* reacts to external events, and so forth)associated with the source user 2*.

In some implementations, the acquisition operation 304 of FIG. 3 mayinclude an operation 546 for acquiring the source user data indicatingthe plurality of reported aspects including one or more incidences ofbelief or beliefs associated with the source user as depicted in FIG. 5c. For instance, the source user data acquisition module 104* of theserver 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d, orthe local end user device 30″ of FIG. 1 f acquiring the source user data14* indicating the plurality of reported aspects including one or moreincidences of belief or beliefs (e.g., religious beliefs, spiritualbeliefs, dietary beliefs, and so forth) associated with the source user2*.

In some implementations, the acquisition operation 304 may include anoperation 547 for acquiring the source user data indicating theplurality of reported aspects including one or more incidences ofsubjective user states associated with the source user as depicted inFIG. 5 c. For instance, the source user data acquisition module 104* ofthe server 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d,or the local end user device 30″ of FIG. 1 f acquiring the source userdata 14* indicating the plurality of reported aspects including one ormore incidences of subjective user states (e.g., “rested,” “well,”“alert,” “occupied,” “relaxed,” and so forth) associated with the sourceuser 2*. For these implementations, incidences of various types ofsubjective user states may be indicated by the acquired source user data14*.

For example, in some implementations, operation 547 may include anoperation 548 for acquiring the source user data indicating theplurality of reported aspects including one or more incidences ofsubjective mental states associated with the source user as depicted inFIG. 5 c. For instance, the source user data acquisition module 104* ofthe server 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d,or the local end user device 30″ of FIG. 1 f acquiring the source userdata 14* indicating the plurality of reported aspects including one ormore incidences of subjective mental states (e.g., happy, relaxed, calm,awake or alert, and so forth) associated with the source user 2*.

In the same or different implementations, operation 547 may include anoperation 549 for acquiring the source user data indicating theplurality of reported aspects including one or more incidences ofsubjective physical states associated with the source user as depictedin FIG. 5 c. For instance, the source user data acquisition module 104*of the server 10 of FIG. 1 b, the local source user device 20′ of FIG. 1d, or the local end user device 30″ of FIG. 1 f acquiring the sourceuser data 14* indicating the plurality of reported aspects including oneor more incidences of subjective physical states (e.g., being fit,having endurance, being pain free, and so forth) associated with thesource user 2*.

In the same or different implementations, operation 547 may include anoperation 550 for acquiring the source user data indicating theplurality of reported aspects including one or more incidences ofsubjective overall user states associated with the source user asdepicted in FIG. 5 c. For instance, the source user data acquisitionmodule 104* of the server 10 of FIG. 1 b, the local source user device20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1 f acquiringthe source user data 14* indicating the plurality of reported aspectsincluding one or more incidences of subjective overall user states(e.g., “good,” “well,” “available,” and so forth) associated with thesource user 2*.

Incidences of other types of aspects associated with a source user 2*may also be indicated by the source user data 14* acquired through theacquisition operation 304 in various alternative implementations. Forexample, in some implementations, the acquisition operation 304 mayinclude an operation 551 for acquiring the source user data indicatingthe plurality of reported aspects including one or more incidences ofuser physical characteristics associated with the source user asdepicted in FIG. 5 d. For instance, the source user data acquisitionmodule 104* of the server 10 of FIG. 1 b, the local source user device20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1 f acquiringthe source user data 14* indicating the plurality of reported aspectsincluding one or more incidences of user physical characteristics (e.g.,hair color, hair length, weight loss, nail color or length, and soforth) associated with the source user 2*.

In some implementations, the acquisition operation 304 may include anoperation 552 for acquiring the source user data indicating theplurality of reported aspects including one or more incidences of userlocations associated with the source user as depicted in FIG. 5 d. Forinstance, the source user data acquisition module 104* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f acquiring the source user data 14*indicating the plurality of reported aspects including one or moreincidences of user locations (e.g., home, workplace, Hawaii, the gym,and so forth) associated with the source user 2*.

In some implementations, the acquisition operation 304 may include anoperation 553 for acquiring the source user data indicating theplurality of reported aspects including one or more incidences ofexternal events associated with the source user as depicted in FIG. 5 d.For instance, the source user data acquisition module 104* of the server10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or thelocal end user device 30″ of FIG. 1 f acquiring the source user data 14*indicating the plurality of reported aspects including one or moreincidences of external events (e.g., weather, drinking water quality,work environment, and so forth) associated with the source user 2*.

In addition to acquiring source user data that indicates a plurality ofreported aspects associated with a source user 2*, the acquisitionoperation 304 of FIG. 3 may involve the acquisition of source user datathat indicates other types of events. For example, in someimplementations, the acquisition operation 304 may include an operation554 for acquiring source user data indicating one or more reportedoutcomes associated with the source user as depicted in FIG. 5 e. Forinstance, the source user data acquisition module 104* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f acquiring source user data 14*indicating one or more reported outcomes (e.g., at least oneintermediate outcome related to the final or target outcome) associatedwith the source user 2*.

Note that a “reported outcome” may be viewed, in some cases, as merelyone type of reported aspect associated with a source user 2*. Forexample, the weight loss of a source user 2* at different points in timemay represent reported outcomes but may also be considered reportedaspects associated with the source user 2* in some cases. For thesecases, the distinction with respect to a reported outcome as opposed to,for example, other types of reported aspects are that a reported outcomemay be the result of or is dependent on the occurrence of other reportedaspects, while other types of reported aspects may not be dependent onthe occurrence of other reported aspects.

In various implementations, operation 554 may include one or moreoperations. For example, in some implementations, operation 554 mayinclude an operation 555 for acquiring source user data indicating aplurality of reported outcomes associated with the source user asdepicted in FIG. 5 e. For instance, the source user data acquisitionmodule 104* of the server 10 of FIG. 1 b, the local source user device20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1 f acquiringsource user data 14* indicating a plurality of reported outcomes (e.g.,blood pressure levels or bowling scores over the course of severalmonths) associated with the source user 2*.

In some implementations, operation 555 may further include an operation556 for acquiring the source user data indicating the plurality ofreported outcomes associated with the source user, at least a first oneof the reported outcomes indicated by the source user data being areported outcome that occurred during a first point or interval of timeand at least a second one of the reported outcomes being a reportedoutcome that occurred during a second point or interval of time, thesecond point or interval of time being a later point or interval of timethan the first point or interval of time as depicted in FIG. 5 e. Forinstance, the source user data acquisition module 104* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f acquiring the source user data 14*indicating the plurality of reported outcomes associated with the sourceuser 2*, at least a first one of the reported outcomes (e.g., a bowlingaverage of 98) indicated by the source user data 14* being a reportedoutcome that occurred during a first point or interval of time and atleast a second one of the reported outcomes (e.g., a bowling average of156) being a reported outcome that occurred during a second point orinterval of time, the second point or interval of time (e.g., May 9,2011) being a later point or interval of time than the first point orinterval of time (e.g., Mar. 2, 2011).

Operation 556, in turn, may further include an operation 557 foracquiring the source user data indicating the plurality of reportedoutcomes associated with the source user, at least the first one of thereported outcomes and the second one of the reported outcomes beingrelated outcomes as depicted in FIG. 5 e. For instance, the source userdata acquisition module 104* of the server 10 of FIG. 1 b, the localsource user device 20′ of FIG. 1 d, or the local end user device 30″ ofFIG. 1 f acquiring source user data 14* indicating the plurality ofreported outcomes associated with the source user 2*, at least the firstone of the reported outcomes and the second one of the reported outcomesbeing related outcomes (e.g., same types of outcomes such as outcomesrelated to weight loss, outcomes related to a particular work skill suchas word processing skills, outcomes related to a particularinterpersonal skill such as developing new friendships, and so forth).

In various implementations, the operation 554 for acquiring source userdata indicating one or more reported outcomes associated with the sourceuser, may further include an operation 558 for acquiring source userdata indicating one or more reported outcomes associated with the sourceuser that corresponds to the one or more target outcomes of thepersonalized plan as depicted in FIG. 5 e. For instance, the source userdata acquisition module 104* of the server 10 of FIG. 1 b, the localsource user device 20′ of FIG. 1 d, or the local end user device 30″ ofFIG. 1 f acquiring source user data 14* indicating one or more reportedoutcomes (e.g., a final reported outcome such as weight loss) associatedwith the source user 2* that corresponds to the one or more targetoutcomes (e.g., a target weight loss) of the personalized plan 16*.

In some implementations, the acquisition operation 304 of FIG. 3 mayinclude an operation 559 for acquiring source user data indicating oneor more reported outcomes including one or more reported physicalcharacteristics of the source user as depicted in FIG. 5 e. Forinstance, the source user data acquisition module 104* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f acquiring source user data 14*indicating one or more reported outcomes including one or more reportedphysical characteristics (e.g., weight, hair color, physiologicalcharacteristic such as hormone level or heart rate at rest, skin tone,hearing characteristic, vision characteristic, and so forth) of thesource user 2*.

In some implementations, the acquisition operation 304 of FIG. 3 mayinclude an operation 560 for acquiring source user data indicating oneor more reported outcomes including one or more reported medical orhealth characteristics of the source user as depicted in FIG. 5 e. Forinstance, the source user data acquisition module 104* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f acquiring source user data 14*indicating one or more reported outcomes including one or more reportedmedical or health characteristics (e.g., reduction in tumor size,absence of a malignant tumor, improved cardiovascular performance, andso forth) of the source user 2*.

In some implementations, the acquisition operation 304 of FIG. 3 mayinclude an operation 561 for acquiring source user data indicating oneor more reported outcomes including one or more reported traits of thesource user as depicted in FIG. 5 e. For instance, the source user dataacquisition module 104* of the server 10 of FIG. 1 b, the local sourceuser device 20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1f acquiring source user data 14* indicating one or more reportedoutcomes including one or more reported traits (e.g., mannerisms,alertness, affect, charisma, demeanor, style, number of friends, wealth,happiness, sadness, order in life, organization, control, well being,spirituality, improved communication, better personal or professionalrelationships, better anger management, better cognitive skills,improved vocabulary, improved problem solving skills, improved copingmechanisms, better math skills, and so forth) of the source user 2*.

In some implementations, the acquisition operation 304 of FIG. 3 mayinclude an operation 562 for acquiring source user data indicating oneor more reported outcomes including one or more reported statuses of thesource user as depicted in FIG. 5 f. For instance, the source user dataacquisition module 104* of the server 10 of FIG. 1 b, the local sourceuser device 20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1f acquiring source user data 14* indicating one or more reportedoutcomes including one or more reported statuses (e.g., availability,wellness, employment, marital, physical or mental states, and so forth)of the source user 2*.

In some implementations, the acquisition operation 304 of FIG. 3 mayinclude an operation 563 for acquiring source user data indicating oneor more reported outcomes including one or more reported athleticoutcomes or skills of the source user as depicted in FIG. 5 f. Forinstance, the source user data acquisition module 104* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f acquiring source user data 14*indicating one or more reported outcomes including one or more reportedathletic outcomes or skills (e.g., reducing golf handicap, swimming onemile, developing a curveball patch, and so forth) of the source user 2*.

In some implementations, the acquisition operation 304 of FIG. 3 mayinclude an operation 564 for acquiring source user data indicating oneor more reported outcomes including one or more reported gaming outcomesor skills of the source user as depicted in FIG. 5 f. For instance, thesource user data acquisition module 104* of the server 10 of FIG. 1 b,the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f acquiring source user data 14* indicating one ormore reported outcomes including one or more reported gaming outcomes orskills (e.g., chess playing results, video/electronic gaming skills, andso forth) of the source user 2*.

In some implementations, the acquisition operation 304 of FIG. 3 mayinclude an operation 565 for acquiring source user data indicating oneor more reported outcomes including one or more reported work outcomesor skills of the source user as depicted in FIG. 5 f. For instance, thesource user data acquisition module 104* of the server 10 of FIG. 1 b,the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f acquiring source user data 14* indicating one ormore reported outcomes including one or more reported work outcomes orskills (e.g., successful completion of a project, computer skills,managerial skills, and so forth) of the source user 2*.

In some implementations, the acquisition operation 304 of FIG. 3 mayinclude an operation 566 for acquiring source user data indicating oneor more reported outcomes including one or more reported leisureoutcomes or skills of the source user as depicted in FIG. 5 f. Forinstance, the source user data acquisition module 104* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f acquiring source user data 14*indicating one or more reported outcomes including one or more reportedleisure outcomes or skills (e.g., having lots of friends, going away ona vacation, having extra time to spend with children, and so forth) ofthe source user 2*.

In some implementations, the acquisition operation 304 of FIG. 3 mayinclude an operation 567 for acquiring source user data indicating oneor more reported outcomes including one or more reported intellectual oracademic outcomes or skills of the source user as depicted in FIG. 5 f.For instance, the source user data acquisition module 104* of the server10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or thelocal end user device 30″ of FIG. 1 f acquiring source user data 14*indicating one or more reported outcomes including one or more reportedintellectual or academic outcomes or skills (e.g., achieving a certaingrade point average or score on a test, increased IQ, comprehension oftechnically complex subject, and so forth) of the source user 2*.

In some implementations, the acquisition operation 304 of FIG. 3 mayinclude an operation 568 for acquiring source user data indicating oneor more reported outcomes including one or more reported sexual intimacyoutcomes associated with the source user as depicted in FIG. 5 f. Forinstance, the source user data acquisition module 104* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f acquiring source user data 14*indicating one or more reported outcomes including one or more reportedsexual intimacy outcomes (e.g., number of or quality of sexualencounters) associated with the source user 2*.

In some implementations, the acquisition operation 304 of FIG. 3 mayinclude an operation 569 for acquiring source user data indicating oneor more reported outcomes including one or more reported externaloutcomes associated with the source user as depicted in FIG. 5 f. Forinstance, the source user data acquisition module 104* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f acquiring source user data 14*indicating one or more reported outcomes including one or more reportedexternal outcomes (e.g., subordinates' work production, behavior ofothers towards the source user 2*, and so forth) associated with thesource user 2*.

Referring back to the development operation 306 of FIG. 3, in variousimplementations, the development operation 306 may be implemented in avariety of different ways. For example, in some implementations, thedevelopment operation 306 may include an operation 670 for developingthe personalized plan by at least determining which of the plurality ofreported aspects occurred within a predefined time period fromoccurrence of one or more reported outcomes associated with the sourceuser that corresponds to the one or more target outcomes of thepersonalized plan as depicted in FIG. 6 a. For instance, thepersonalized plan development module 106* of the server 10 of FIG. 1 b,the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f developing the personalized plan 16* based on therelevant reported aspect determination module 208* at least determiningwhich of the plurality of reported aspects (e.g., as indicated by thesource user data 14*) occurred within a predefined time period fromoccurrence of one or more reported outcomes (e.g., weight loss of 20pounds) associated with the source user 2* (e.g., as indicated by thesource user data 14*) that corresponds to the one or more targetoutcomes (e.g., weight loss 20 pounds) of the personalized plan 16*.

Operation 670 may, in certain implementations, include an operation 671for developing the personalized plan by at least determining which ofthe plurality of reported aspects occurred within a predefined timeperiod and preceded occurrence of the one or more reported outcomesassociated with the source user that corresponds to the one or moretarget outcomes of the personalized plan as depicted in FIG. 6 a. Forinstance, the personalized plan development module 106* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f developing the personalized plan 16*based on the relevant reported aspect determination module 208*at leastdetermining which of the plurality of reported aspects (e.g., asindicated by the source user data 14*) occurred within a predefined timeperiod and preceded occurrence of the one or more reported outcomesassociated with the source user 2*(e.g., as indicated by the source userdata 14*) that corresponds to the one or more target outcomes of thepersonalized plan 16*.

In some implementations, the development operation 306 of FIG. 3 mayinclude an operation 672 for developing the personalized plan by atleast determining which of the plurality of reported aspects arerelevant to the achievement of the one or more target outcomes based onone or more indications provided by the source user as depicted in FIG.6 a. For instance, the personalized plan development module 106* of theserver 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d, orthe local end user device 30″ of FIG. 1 f developing the personalizedplan 16* based on the relevant reported aspect determination module 208*at least determining which of the plurality of reported aspects (e.g.,as indicated by the source user data 14*) are relevant to theachievement of the one or more target outcomes based on one or moreindications provided by the source user 2*. In other words, the sourceuser 2* may provide an indication as to which of the reported aspectsmay be relevant to the achievement of the one or more target outcomes ofthe personalized plan 16*.

In some cases, operation 672 may further include one or more additionaloperations. For example, in some implementations, operation 672 mayinclude an operation 673 for requesting the source user to provide oneor more indications of which of the reported aspects are relevant toachievement of one or more reported outcomes that corresponds to the oneor more target outcomes of the personalized plan as depicted in FIG. 6a. For example, the reported aspect relevancy requesting module 212* ofthe server 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d,or the local end user device 30″ of FIG. 1 f requesting the source user2*(e.g., transmitting a request 12* via a wireless network and/or wirednetwork 50* or indicating a request 12* via a user interface 120′) toprovide one or more indications of which of the reported aspects (e.g.,as indicated by the acquired source user data 14*) are relevant toachievement of one or more reported outcomes (e.g., as indicated by, forexample, the acquired source user data 14*) that corresponds to the oneor more target outcomes of the personalized plan 16*. For theseimplementations, the source user 2* may be requested to merely indicatewhat type or types of reported aspects (e.g., reduced carbohydrateintake) may be relevant to the achievement of the one or more reportedoutcomes (e.g., weight loss of 30 pounds).

In some implementations, operation 672 may include an operation 674 forrequesting the source user to provide one or more indications of whichof the reported aspects are not relevant to achievement of one or morereported outcomes that corresponds to the one or more target outcomes ofthe personalized plan as depicted in FIG. 6 a. For instance, thereported aspect non-relevancy requesting module 214* of the server 10 ofFIG. 1 b, the local source user device 20′ of FIG. 1 d, or the local enduser device 30″ of FIG. 1 f requesting the source user 2*(e.g.,transmitting a request 12* via a wireless network and/or wired network50* or indicating a request 12* via a user interface 120′) to provideone or more indications of which of the reported aspects (e.g., asindicated by the acquired source user data 14*) are not relevant toachievement of one or more reported outcomes (e.g., as indicated by theacquired source user data 14*) that corresponds to the one or moretarget outcomes of the personalized plan 16*. For these implementations,the source user 2* may be requested to merely indicate what type ortypes of reported aspects (e.g., getting 8 hours of sleep) may not berelevant to the achievement of the one or more reported outcomes (e.g.,weight loss of 30 pounds).

In various implementations, the development of a personalized plan 16*through the development operation 306 of FIG. 3 may be based, at leastin part, on input provided by an end user 4*. For example, thedevelopment operation 306 in various implementations may include anoperation 675 for developing the personalized plan by at leastdetermining which of the plurality of reported aspects are relevant tothe achievement of the one or more target outcomes based on one or moreindications provided by the end user as depicted in FIG. 6 b. Forinstance, the personalized plan development module 106* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f developing the personalized plan 16* asa result of the relevant reported aspect determination module 208* atleast determining which of the plurality of reported aspects (e.g., asindicated by the acquired source user data 14*) are relevant to theachievement of the one or more target outcomes based on one or moreindications provided by the end user 4*.

In various alternative implementations, operation 675 may furtherinclude one or more additional operations. For example, in someimplementations, operation 675 may include an operation 676 forrequesting the end user to provide one or more indications of which ofthe reported aspects are relevant to achievement of one or more reportedoutcomes that corresponds to the one or more target outcomes of thepersonalized plan as depicted in FIG. 6 b. For example, the reportedaspect relevancy requesting module 212* of the server 10 of FIG. 1 b,the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f requesting the end user 4*(e.g., transmitting arequest 12* via a wireless network and/or wired network 50* orindicating a request 12* via a user interface 120″) to provide one ormore indications of which of the reported aspects (e.g., as indicated bythe acquired source user data 14*) are relevant to achievement of one ormore reported outcomes (e.g., as indicated by, for example, the acquiredsource user data 14*) that corresponds to the one or more targetoutcomes of the personalized plan 16*.

In some implementations, operation 675 may include an operation 677 forrequesting the end user to provide one or more indications of which ofthe reported aspects are not relevant to achievement of one or morereported outcomes that corresponds to the one or more target outcomes ofthe personalized plan as depicted in FIG. 6 b. For instance, thereported aspect non-relevancy requesting module 214* of the server 10 ofFIG. 1 b, the local source user device 20′ of FIG. 1 d, or the local enduser device 30″ of FIG. 1 f requesting the end user 4*(e.g.,transmitting a request 12* via a wireless network and/or wired network50* or indicating a request 12* via a user interface 120″) to provideone or more indications of which of the reported aspects (e.g., asindicated by the acquired source user data 14*) are not relevant toachievement of one or more reported outcomes (e.g., as indicated by, forexample, the acquired source user data 14*) that corresponds to the oneor more target outcomes of the personalized plan 16*.

In various implementations, operation 675 may include an operation 678for requesting the end user to provide one or more indications of whattypes of aspects are relevant to the achievement of the one or moretarget outcomes of the personalized plan as depicted in FIG. 6 b. Forinstance, the aspect type relevancy requesting module 216* of the server10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or thelocal end user device 30″ of FIG. 1 f requesting the end user 4*(e.g.,transmitting a request 12* via a wireless network and/or wired network50* or indicating a request 12* via a user interface 120″) to provideone or more indications of what types of aspects (e.g., what types ofbooks should be read) are relevant to the achievement of the one or moretarget outcomes (e.g., improve reading test score) of the personalizedplan 16*.

In some implementations, operation 678 may further include an operation679 for determining which of the plurality of reported aspects belong toone or more types of aspects, as indicated by the end user, as beingrelevant to the achievement of the one or more target outcomes of thepersonalized plan as depicted in FIG. 6 b. For instance, the relevantreported aspect determination module 208* of the server 10 of FIG. 1 b,the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f determining which of the plurality of reportedaspects (e.g., as indicated by the acquired source user data 14*) belongto one or more types of aspects, as indicated by the end user 4*, asbeing relevant to the achievement of the one or more target outcomes ofthe personalized plan 16*.

In various implementations, operation 675 may include an operation 680for requesting the end user to provide indications of what types ofaspects are not relevant to the achievement of the one or more targetoutcomes of the personalized plan as depicted in FIG. 6 b. For instance,the aspect type non-relevancy requesting module 218* of the server 10 ofFIG. 1 b, the local source user device 20′ of FIG. 1 d, or the local enduser device 30″ of FIG. 1 f requesting the end user 4*(e.g.,transmitting a request 12* via a wireless network and/or wired network50* or indicating a request 12* via a user interface 120″) to provideone or more indications of what types of aspects are relevant to theachievement of the one or more target outcomes of the personalized plan16*.

In some implementations, operation 680 may further include an operation681 for determining which of the plurality of reported aspects does notbelong to one or more types of aspects, as indicated by the end user, asbeing not relevant to the achievement of the one or more target outcomesof the personalized plan as depicted in FIG. 6 b. For instance, therelevant reported aspect determination module 208* of the server 10 ofFIG. 1 b, the local source user device 20′ of FIG. 1 d, or the local enduser device 30″ of FIG. 1 f determining which of the plurality ofreported aspects (e.g., as indicated by the acquired source user data14*) does not belong to one or more types of aspects, as indicated bythe end user 4*, as being not relevant to the achievement of the one ormore target outcomes of the personalized plan 16*.

In various implementations, the development operation 306 of FIG. 3 mayinclude an operation 682 for developing the personalized plan by atleast determining which of the plurality of reported aspects arerelevant to the achievement of the one or more target outcomes based, atleast in part, on data provided by one or more third party sources thatindicates one or more types of aspects that are relevant to theachievement of the one or more target outcomes of the personalized planas depicted in FIG. 6 c. For instance, the personalized plan developmentmodule 106* of the server 10 of FIG. 1 b, the local source user device20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1 f developingthe personalized plan 16* as a result of the relevant reported aspectdetermination module 208* at least determining which of the plurality ofreported aspects (e.g., as indicated by the acquired source user data14*) are relevant to the achievement of the one or more target outcomesbased, at least in part, on data provided by one or more third partysources (e.g., other source or end users 4*, publications, researchpapers, medical research, and so forth) that indicates one or more typesof aspects that are relevant to the achievement of the one or moretarget outcomes of the personalized plan 16*.

In various embodiments, the development operation 306 may include anoperation 683 for developing the personalized plan by including into thepersonalized plan at least one emulatable aspect that corresponds to atleast one reported aspect associated with the source user that isdetermined to be relevant to the achievement of the one or more targetoutcomes as depicted in FIG. 6 c. For instance, the personalized plandevelopment module 106* of the server 10 of FIG. 1 b, the local sourceuser device 20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1f developing the personalized plan 16* by having the emulatable aspectinclusion module 222* include into the personalized plan 16* at leastone emulatable aspect that corresponds to at least one reported aspectassociated with the source user 2* that is determined to be relevant tothe achievement of the one or more target outcomes of the personalizedplan 16*.

In some implementations, the development operation 306 may include, invarious alternative implementations, an operation 684 for developing thepersonalized plan by including into the personalized plan at least oneintermediate outcome that corresponds to one or more reportedintermediate outcomes as indicated by the source user data as depictedin FIG. 6 c. For instance, the personalized plan development module 106*of the server 10 of FIG. 1 b, the local source user device 20′ of FIG. 1d, or the local end user device 30″ of FIG. 1 f developing thepersonalized plan 16* by having the intermediate outcome inclusionmodule 224* include into the personalized plan 16* at least oneintermediate outcome that corresponds to one or more reportedintermediate outcomes as indicated by the source user data 14*. Notethat an intermediate outcome is an outcome that may precede the finalreported outcome (e.g., target outcome associated with a personalizedplan 16*). The intermediate outcome may be used in order to track, forexample, the progress of an end user 4* in achieving a target outcomeassociated with a personalized plan 16*.

In some implementations, the development operation 306 may include anoperation 685 for developing the personalized plan by including into thepersonalized plan a plurality of emulatable aspects that corresponds tothe plurality of reported aspects associated with the source user thatare determined to be relevant to the achievement of the one or moretarget outcomes as depicted in FIG. 6 c. For instance, the personalizedplan development module 106* of the server 10 of FIG. 1 b, the localsource user device 20′ of FIG. 1 d, or the local end user device 30″ ofFIG. 1 f developing the personalized plan 16* by having the emulatableaspect inclusion module 222* include into the personalized plan 16* aplurality of emulatable aspects that corresponds to the plurality ofreported aspects (e.g., as indicated by the acquired source user data14*) associated with the source user 2* that are determined to berelevant to the achievement of the one or more target outcomes of thepersonalized plan 16*.

Operation 685, in turn, may further include one or more additionaloperations as illustrated in FIG. 6 d. For example, in someimplementations, operation 685 may include an operation 686 fordeveloping the personalized plan by defining in the personalized plan arelationship or relationships between the plurality of emulatableaspects included in the personalized plan. For instance, thepersonalized plan development module 106* of the server 10 of FIG. 1 b,the local source user device 20′ of FIG. 1 d, or the local end userdevice 30″ of FIG. 1 f developing the personalized plan 16* by havingthe relationship defining module 226* define in the personalized plan16* a relationship or relationships (e.g., temporal relationships,specific time relationships, or spatial relationships) between theplurality of emulatable aspects included in the personalized plan 16.Note that in some implementations, the personalized plan 16* may notindicate the relationships between the plurality of emulatable aspectsincluded in the personalized plan 16*. Instead, such a personalized plan16* may simply be a collection of emulatable aspects (as well as in somecases a collection of one or more outcomes).

In various implementations, operation 686 may further include anoperation 687 for developing the personalized plan by defining in thepersonalized plan a temporal relationship or relationships between theplurality of emulatable aspects included in the personalized plan asdepicted in FIG. 6 d. For instance, the personalized plan developmentmodule 106* of the server 10 of FIG. 1 b, the local source user device20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1 f developingthe personalized plan 16* by having the relationship defining module226* define in the personalized plan 16* a temporal relationship orrelationships between the plurality of emulatable aspects included inthe personalized plan 16*.

In some implementations, operation 686 may include an operation 688 fordeveloping the personalized plan by defining in the personalized plan aspecific time relationship or relationships between the plurality ofemulatable aspects included in the personalized plan as depicted in FIG.6 d. For instance, the personalized plan development module 106* of theserver 10 of FIG. 1 b, the local source user device 20′ of FIG. 1 d, orthe local end user device 30″ of FIG. 1 f developing the personalizedplan 16* by having the relationship defining module 226* define in thepersonalized plan 16* a specific time relationship or relationshipsbetween the plurality of emulatable aspects included in the personalizedplan 16*.

In various implementations, operation 686 may further include anoperation 689 for developing the personalized plan by defining in thepersonalized plan a spatial relationship or relationships between theplurality of emulatable aspects included in the personalized plan asdepicted in FIG. 6 d. For instance, the personalized plan developmentmodule 106* of the server 10 of FIG. 1 b, the local source user device20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1 f developingthe personalized plan 16* by having the relationship defining module226* define in the personalized plan 16* a spatial relationship orrelationships between the plurality of emulatable aspects included inthe personalized plan 16*.

In various implementations, operation 306 of FIG. 3 may include anoperation 690 for developing the personalized plan by including into thepersonalized plan at least one plausible emulatable aspect, the at leastone plausible emulatable aspect being at least one emulatable aspectthat has been successfully emulated by one or more other end users asdepicted in FIG. 6 d. For instance, the personalized plan developmentmodule 106* of the server 10 of FIG. 1 b, the local source user device20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1 f developingthe personalized plan 16* by having the plausible emulatable aspectinclusion module 228* include into the personalized plan 16* at leastone plausible emulatable aspect, the at least one plausible emulatableaspect being at least one emulatable aspect that has been successfullyemulated by one or more other end users 4*(e.g., one or more thirdparties 6*).

Operation 690 may, in turn, include an operation 691 for developing thepersonalized plan by including into the personalized plan at least oneplausible emulatable aspect, the at least one plausible emulatableaspect being at least one emulatable aspect that has been successfullyemulated by the one or more other end users in order to achieve at leastone of the one or more target outcomes as depicted in FIG. 6 d. Forinstance, the personalized plan development module 106* of the server 10of FIG. 1 b, the local source user device 20′ of FIG. 1 d, or the localend user device 30″ of FIG. 1 f developing the personalized plan 16* byhaving the plausible emulatable aspect inclusion module 228 include intothe personalized plan 16* at least one plausible emulatable aspect, theat least one plausible emulatable aspect being at least one emulatableaspect that has been successfully emulated by one or more other endusers in order to achieve at least one of the one or more targetoutcomes of the personalized plan 16*.

Referring to FIG. 7 illustrating another operational flow 700 inaccordance with various embodiments. Operational flow 700 includescertain operations that mirror the operations included in theoperational flow 300 of FIG. 3. These operations include a receptionoperation 702, an acquisition operation 704 and a development operation706 that corresponds to and mirror the reception operation 302, theacquisition operation 304 and the development operation 306,respectively, of FIG. 3.

In addition, operational flow 700 includes a presentation operation 708for presenting the personalized plan as depicted in FIG. 7. Forinstance, the presentation module 108* of the server 10 of FIG. 1 b, thelocal source user device 20′ of FIG. 1 d, or the local end user device30″ of FIG. 1 f presenting (e.g., transmitting via the wireless networkand/or wired network 50 or indicating via a user interface 120*) thepersonalized plan 16*.

In various alternative implementations, the presentation operation 708may include one or more additional operations. For example, in someimplementations, the presentation operation 708 may include an operation893 for transmitting the personalized plan via at least one of wirelessnetwork and a wired network as depicted in FIG. 8. For instance, thetransmission module 228* of the server 10 of FIG. 1 b, the local sourceuser device 20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1f transmitting the personalized plan 16* via at least one of wirelessnetwork and a wired network 50*.

In the same or different implementations, the presentation operation 708may include an operation 894 for indicating the personalized plan via auser interface as depicted in FIG. 8. For instance, the user interfaceindication module 229* of the local source user device 20′ of FIG. 1 dor the local end user device 30″ of FIG. 1 f audioally or visuallyindicating the personalized plan 16* via a user interface 120*(e.g., adisplay monitor, a touchscreen, an audio system including one or morespeakers, and so forth).

In the same or different implementations, the presentation operation 708may include an operation 895 for presenting the personalized plan to theend user as depicted in FIG. 8. For instance, the presentation module108* of the server 10 of FIG. 1 b, the local source user device 20′ ofFIG. 1 d, or the local end user device 30″ of FIG. 1 f presenting thepersonalized plan 16* to the end user 4*.

In the same or different implementations, the presentation operation 708may include an operation 896 for presenting the personalized plan to oneor more third parties as depicted in FIG. 8. For instance, thepresentation module 108* of the server 10 of FIG. 1 b, the local sourceuser device 20′ of FIG. 1 d, or the local end user device 30″ of FIG. 1f presenting the personalized plan 16* to one or more third parties 6*.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware and software implementations of aspects of systems; theuse of hardware or software is generally (but not always, in that incertain contexts the choice between hardware and software can becomesignificant) a design choice representing cost vs. efficiency tradeoffs.Those having skill in the art will appreciate that there are variousvehicles by which processes and/or systems and/or other technologiesdescribed herein can be effected (e.g., hardware, software, and/orfirmware), and that the preferred vehicle will vary with the context inwhich the processes and/or systems and/or other technologies aredeployed. For example, if an implementer determines that speed andaccuracy are paramount, the implementer may opt for a mainly hardwareand/or firmware vehicle; alternatively, if flexibility is paramount, theimplementer may opt for a mainly software implementation; or, yet againalternatively, the implementer may opt for some combination of hardware,software, and/or firmware. Hence, there are several possible vehicles bywhich the processes and/or devices and/or other technologies describedherein may be effected, none of which is inherently superior to theother in that any vehicle to be utilized is a choice dependent upon thecontext in which the vehicle will be deployed and the specific concerns(e.g., speed, flexibility, or predictability) of the implementer, any ofwhich may vary. Those skilled in the art will recognize that opticalaspects of implementations will typically employ optically-orientedhardware, software, and or firmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuitry (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuitry, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link, etc.).

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware, orany combination thereof can be viewed as being composed of various typesof “electrical circuitry.” Consequently, as used herein “electricalcircuitry” includes, but is not limited to, electrical circuitry havingat least one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of randomaccess memory), and/or electrical circuitry forming a communicationsdevice (e.g., a modem, communications switch, or optical-electricalequipment). Those having skill in the art will recognize that thesubject matter described herein may be implemented in an analog ordigital fashion or some combination thereof.

Those having skill in the art will recognize that it is common withinthe art to describe devices and/or processes in the fashion set forthherein, and thereafter use engineering practices to integrate suchdescribed devices and/or processes into data processing systems. Thatis, at least a portion of the devices and/or processes described hereincan be integrated into a data processing system via a reasonable amountof experimentation. Those having skill in the art will recognize that atypical data processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices, such as a touch pad or screen, and/or controlsystems including feedback loops and control motors (e.g., feedback forsensing position and/or velocity; control motors for moving and/oradjusting components and/or quantities). A typical data processingsystem may be implemented utilizing any suitable commercially availablecomponents, such as those typically found in datacomputing/communication and/or network computing/communication systems.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.Furthermore, it is to be understood that the invention is defined by theappended claims.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to inventions containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations.

In addition, even if a specific number of an introduced claim recitationis explicitly recited, those skilled in the art will recognize that suchrecitation should typically be interpreted to mean at least the recitednumber (e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.).

In those instances where a convention analogous to “at least one of A,B, or C, etc.” is used, in general such a construction is intended inthe sense one having skill in the art would understand the convention(e.g., “a system having at least one of A, B, or C” would include butnot be limited to systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc.). It will be further understood by those within the artthat virtually any disjunctive word and/or phrase presenting two or morealternative terms, whether in the description, claims, or drawings,should be understood to contemplate the possibilities of including oneof the terms, either of the terms, or both terms. For example, thephrase “A or B” will be understood to include the possibilities of “A”or “B” or “A and B.”

1-96. (canceled)
 97. A computationally-implemented system, comprising:means for receiving a request for a personalized plan designed tofacilitate an end user to achieve one or more target outcomes when oneor more emulatable aspects indicated by the personalized plan areemulated, the request identifying at least a source user; means foracquiring source user data indicating a plurality of reported aspectsassociated with at least the source user in response to receiving therequest; and means for developing the personalized plan by at leastdetermining which of the plurality of reported aspects associated withthe source user are relevant to the achievement of the one or moretarget outcomes. 98-113. (canceled)
 114. The computationally-implementedsystem of claim 97, wherein said means for receiving a request for apersonalized plan designed to facilitate an end user to achieve one ormore target outcomes when one or more emulatable aspects indicated bythe personalized plan are emulated, the request identifying at least asource user comprises: means for receiving the request for thepersonalized plan designed to facilitate the end user to achieve the oneor more target outcomes when the one or more emulatable aspectsindicated by the personalized plan are emulated, the request includingan identifier associated with at least the source user.
 115. Thecomputationally-implemented system of claim 97, wherein said means forreceiving a request for a personalized plan designed to facilitate anend user to achieve one or more target outcomes when one or moreemulatable aspects indicated by the personalized plan are emulated, therequest identifying at least a source user comprises: means forreceiving the request for the personalized plan designed to facilitatethe end user to achieve the one or more target outcomes when the one ormore emulatable aspects indicated by the personalized plan are emulated,the request identifying at least one of the one or more target outcomes.116. (canceled)
 117. The computationally-implemented system of claim 97,wherein said means for receiving a request for a personalized plandesigned to facilitate an end user to achieve one or more targetoutcomes when one or more emulatable aspects indicated by thepersonalized plan are emulated, the request identifying at least asource user comprises: means for receiving the request for thepersonalized plan designed to facilitate the end user to achieve the oneor more target outcomes when the one or more emulatable aspectsindicated by the personalized plan are emulated, the request indicatingone or more preferences of the end user.
 118. Thecomputationally-implemented system of claim 97, wherein said means forreceiving a request for a personalized plan designed to facilitate anend user to achieve one or more target outcomes when one or moreemulatable aspects indicated by the personalized plan are emulated, therequest identifying at least a source user comprises: means forreceiving the request for the personalized plan designed to facilitatethe end user to achieve the one or more target outcomes when the one ormore emulatable aspects indicated by the personalized plan are emulated,the request indicating one or more limitations associated with the enduser.
 119. The computationally-implemented system of claim 118, whereinsaid means for receiving the request for the personalized plan designedto facilitate the end user to achieve the one or more target outcomeswhen the one or more emulatable aspects indicated by the personalizedplan are emulated, the request indicating one or more limitationsassociated with the end user comprises: means for receiving the requestfor the personalized plan designed to facilitate the end user to achievethe one or more target outcomes when the one or more emulatable aspectsindicated by the personalized plan are emulated, the request indicatingone or more physical limitations associated with the end user.
 120. Thecomputationally-implemented system of claim 118, wherein said means forreceiving the request for the personalized plan designed to facilitatethe end user to achieve the one or more target outcomes when the one ormore emulatable aspects indicated by the personalized plan are emulated,the request indicating one or more limitations associated with the enduser comprises: means for receiving the request for the personalizedplan designed to facilitate the end user to achieve the one or moretarget outcomes when the one or more emulatable aspects indicated by thepersonalized plan are emulated, the request indicating one or morecontextual limitations associated with the end user.
 121. Thecomputationally-implemented system of claim 118, wherein said means forreceiving the request for the personalized plan designed to facilitatethe end user to achieve the one or more target outcomes when the one ormore emulatable aspects indicated by the personalized plan are emulated,the request indicating one or more limitations associated with the enduser comprises: means for receiving the request for the personalizedplan designed to facilitate the end user to achieve the one or moretarget outcomes when the one or more emulatable aspects indicated by thepersonalized plan are emulated, the request indicating one or morepersonal limitations associated with the end user.
 122. Thecomputationally-implemented system of claim 118, wherein said means forreceiving the request for the personalized plan designed to facilitatethe end user to achieve the one or more target outcomes when the one ormore emulatable aspects indicated by the personalized plan are emulated,the request indicating one or more limitations associated with the enduser comprises: means for receiving the request for the personalizedplan designed to facilitate the end user to achieve the one or moretarget outcomes when the one or more emulatable aspects indicated by thepersonalized plan are emulated, the request indicating one or moremedical or health limitations associated with the end user.
 123. Thecomputationally-implemented system of claim 118, wherein said means forreceiving the request for the personalized plan designed to facilitatethe end user to achieve the one or more target outcomes when the one ormore emulatable aspects indicated by the personalized plan are emulated,the request indicating one or more limitations associated with the enduser comprises: means for receiving the request for the personalizedplan designed to facilitate the end user to achieve the one or moretarget outcomes when the one or more emulatable aspects indicated by thepersonalized plan are emulated, the request indicating one or more userstate limitations associated with the end user.
 124. Thecomputationally-implemented system of claim 118, wherein said means forreceiving the request for the personalized plan designed to facilitatethe end user to achieve the one or more target outcomes when the one ormore emulatable aspects indicated by the personalized plan are emulated,the request indicating one or more limitations associated with the enduser comprises: means for receiving the request for the personalizedplan designed to facilitate the end user to achieve the one or moretarget outcomes when the one or more emulatable aspects indicated by thepersonalized plan are emulated, the request indicating one or more legalor regulatory limitations associated with the end user. 125-128.(canceled)
 129. The computationally-implemented system of claim 97,wherein said means for acquiring source user data indicating a pluralityof reported aspects associated with at least the source user in responseto receiving the request comprises: means for acquiring the source userdata including data indicating one or more reported aspects as at leastoriginally reported by the source user.
 130. Thecomputationally-implemented system of claim 97, wherein said means foracquiring source user data indicating a plurality of reported aspectsassociated with at least the source user in response to receiving therequest comprises: means for acquiring the source user data includingdata indicating one or more reported aspects as at least originallyreported by one or more sensors.
 131. (canceled)
 132. Thecomputationally-implemented system of claim 97, wherein said means foracquiring source user data indicating a plurality of reported aspectsassociated with at least the source user in response to receiving therequest comprises: means for acquiring the source user data includingdata indicating one or more reported aspects as at least originallyreported via one or more social networking entries.
 133. Thecomputationally-implemented system of claim 132, wherein said means foracquiring the source user data including data indicating one or morereported aspects as at least originally reported via one or more socialnetworking entries comprises: means for acquiring the source user dataincluding data indicating one or more reported aspects as at leastoriginally reported via one or more blog entries.
 134. Thecomputationally-implemented system of claim 132, wherein said means foracquiring the source user data including data indicating one or morereported aspects as at least originally reported via one or more socialnetworking entries comprises: means for acquiring the source user dataincluding data indicating one or more reported aspects as at leastoriginally reported via one or more status reports.
 135. Thecomputationally-implemented system of claim 97, wherein said means foracquiring source user data indicating a plurality of reported aspectsassociated with at least the source user in response to receiving therequest comprises: means for acquiring the source user data includingdata indicating one or more reported aspects as at least originallyreported via one or more diary entries. 136-142. (canceled)
 143. Thecomputationally-implemented system of claim 97, wherein said means foracquiring source user data indicating a plurality of reported aspectsassociated with at least the source user in response to receiving therequest comprises: means for acquiring the source user data indicatingthe plurality of reported aspects including one or more incidences ofsubjective user states associated with the source user.
 144. Thecomputationally-implemented system of claim 143, wherein said means foracquiring the source user data indicating the plurality of reportedaspects including one or more incidences of subjective user statesassociated with the source user comprises: means for acquiring thesource user data indicating the plurality of reported aspects includingone or more incidences of subjective mental states associated with thesource user.
 145. The computationally-implemented system of claim 143,wherein said means for acquiring the source user data indicating theplurality of reported aspects including one or more incidences ofsubjective user states associated with the source user comprises: meansfor acquiring the source user data indicating the plurality of reportedaspects including one or more incidences of subjective physical statesassociated with the source user.
 146. The computationally-implementedsystem of claim 143, wherein said means for acquiring the source userdata indicating the plurality of reported aspects including one or moreincidences of subjective user states associated with the source usercomprises: means for acquiring the source user data indicating theplurality of reported aspects including one or more incidences ofsubjective overall user states associated with the source user. 147-165.(canceled)
 166. The computationally-implemented system of claim 97,wherein said means for developing the personalized plan by at leastdetermining which of the plurality of reported aspects associated withthe source user are relevant to the achievement of the one or moretarget outcomes comprises: means for developing the personalized plan byat least determining which of the plurality of reported aspects occurredwithin a predefined time period from occurrence of one or more reportedoutcomes associated with the source user that corresponds to the one ormore target outcomes of the personalized plan.
 167. Thecomputationally-implemented system of claim 166, wherein said means fordeveloping the personalized plan by at least determining which of theplurality of reported aspects occurred within a predefined time periodfrom occurrence of one or more reported outcomes associated with thesource user that corresponds to the one or more target outcomes of thepersonalized plan comprises: means for developing the personalized planby at least determining which of the plurality of reported aspectsoccurred within a predefined time period and preceded occurrence of theone or more reported outcomes associated with the source user thatcorresponds to the one or more target outcomes of the personalized plan.168. The computationally-implemented system of claim 97, wherein saidmeans for developing the personalized plan by at least determining whichof the plurality of reported aspects associated with the source user arerelevant to the achievement of the one or more target outcomescomprises: means for developing the personalized plan by at leastdetermining which of the plurality of reported aspects are relevant tothe achievement of the one or more target outcomes based on one or moreindications provided by the source user.
 169. Thecomputationally-implemented system of claim 168, wherein said means fordeveloping the personalized plan by at least determining which of theplurality of reported aspects are relevant to the achievement of the oneor more target outcomes based on one or more indications provided by thesource user comprises: means for requesting the source user to provideone or more indications of which of the reported aspects are relevant toachievement of one or more reported outcomes that corresponds to the oneor more target outcomes of the personalized plan.
 170. Thecomputationally-implemented system of claim 168, wherein said means fordeveloping the personalized plan by at least determining which of theplurality of reported aspects are relevant to the achievement of the oneor more target outcomes based on one or more indications provided by thesource user comprises: means for requesting the source user to provideone or more indications of which of the reported aspects are notrelevant to achievement of one or more reported outcomes thatcorresponds to the one or more target outcomes of the personalized plan.171. The computationally-implemented system of claim 97, wherein saidmeans for developing the personalized plan by at least determining whichof the plurality of reported aspects associated with the source user arerelevant to the achievement of the one or more target outcomescomprises: means for developing the personalized plan by at leastdetermining which of the plurality of reported aspects are relevant tothe achievement of the one or more target outcomes based on one or moreindications provided by the end user.
 172. Thecomputationally-implemented system of claim 171, wherein said means fordeveloping the personalized plan by at least determining which of theplurality of reported aspects are relevant to the achievement of the oneor more target outcomes based on one or more indications provided by theend user comprises: means for requesting the end user to provide one ormore indications of which of the reported aspects are relevant toachievement of one or more reported outcomes that corresponds to the oneor more target outcomes of the personalized plan.
 173. Thecomputationally-implemented system of claim 171, wherein said means fordeveloping the personalized plan by at least determining which of theplurality of reported aspects are relevant to the achievement of the oneor more target outcomes based on one or more indications provided by theend user comprises: means for requesting the end user to provide one ormore indications of which of the reported aspects are not relevant toachievement of one or more reported outcomes that corresponds to the oneor more target outcomes of the personalized plan.
 174. Thecomputationally-implemented system of claim 171, wherein said means fordeveloping the personalized plan by at least determining which of theplurality of reported aspects are relevant to the achievement of the oneor more target outcomes based on one or more indications provided by theend user comprises: means for requesting the end user to provide one ormore indications of what types of aspects are relevant to theachievement of the one or more target outcomes of the personalized plan.175. The computationally-implemented system of claim 174, wherein saidmeans for requesting the end user to provide one or more indications ofwhat types of aspects are relevant to the achievement of the one or moretarget outcomes of the personalized plan comprises: means fordetermining which of the plurality of reported aspects belong to one ormore types of aspects, as indicated by the end user, as being relevantto the achievement of the one or more target outcomes of thepersonalized plan.
 176. The computationally-implemented system of claim171, wherein said means for developing the personalized plan by at leastdetermining which of the plurality of reported aspects are relevant tothe achievement of the one or more target outcomes based on one or moreindications provided by the end user comprises: means for requesting theend user to provide indications of what types of aspects are notrelevant to the achievement of the one or more target outcomes of thepersonalized plan.
 177. The computationally-implemented system of claim176, wherein said means for requesting the end user to provideindications of what types of aspects are not relevant to the achievementof the one or more target outcomes of the personalized plan comprises:means for determining which of the plurality of reported aspects doesnot belong to one or more types of aspects, as indicated by the enduser, as being not relevant to the achievement of the one or more targetoutcomes of the personalized plan.
 178. The computationally-implementedsystem of claim 97, wherein said means for developing the personalizedplan by at least determining which of the plurality of reported aspectsassociated with the source user are relevant to the achievement of theone or more target outcomes comprises: means for developing thepersonalized plan by at least determining which of the plurality ofreported aspects are relevant to the achievement of the one or moretarget outcomes based, at least in part, on data provided by one or morethird party sources that indicates one or more types of aspects that arerelevant to the achievement of the one or more target outcomes of thepersonalized plan.
 179. The computationally-implemented system of claim97, wherein said means for developing the personalized plan by at leastdetermining which of the plurality of reported aspects associated withthe source user are relevant to the achievement of the one or moretarget outcomes comprises: means for developing the personalized plan byincluding into the personalized plan at least one emulatable aspect thatcorresponds to at least one reported aspect associated with the sourceuser that is determined to be relevant to the achievement of the one ormore target outcomes.
 180. The computationally-implemented system ofclaim 97, wherein said means for developing the personalized plan byincluding into the personalized plan at least one emulatable aspect thatcorresponds to at least one reported aspect associated with the sourceuser that is determined to be relevant to the achievement of the one ormore target outcomes developing the personalized plan by at leastdetermining which of the plurality of reported aspects associated withthe source user are relevant to the achievement of the one or moretarget outcomes comprises: means for developing the personalized plan byincluding into the personalized plan at least one intermediate outcomethat corresponds to one or more reported intermediate outcomes asindicated by the source user data.
 181. The computationally-implementedsystem of claim 97, wherein said means for developing the personalizedplan by at least determining which of the plurality of reported aspectsassociated with the source user are relevant to the achievement of theone or more target outcomes comprises: means for developing thepersonalized plan by including into the personalized plan a plurality ofemulatable aspects that corresponds to the plurality of reported aspectsassociated with the source user that are determined to be relevant tothe achievement of the one or more target outcomes.
 182. Thecomputationally-implemented system of claim 181, wherein said means fordeveloping the personalized plan by including into the personalized plana plurality of emulatable aspects that corresponds to the plurality ofreported aspects associated with the source user that are determined tobe relevant to the achievement of the one or more target outcomescomprises: means for developing the personalized plan by defining in thepersonalized plan a relationship or relationships between the pluralityof emulatable aspects included in the personalized plan.
 183. Thecomputationally-implemented system of claim 182, wherein said means fordeveloping the personalized plan by defining in the personalized plan arelationship or relationships between the plurality of emulatableaspects included in the personalized plan comprises: means fordeveloping the personalized plan by defining in the personalized plan atemporal relationship or relationships between the plurality ofemulatable aspects included in the personalized plan.
 184. Thecomputationally-implemented system of claim 182, wherein said means fordeveloping the personalized plan by defining in the personalized plan arelationship or relationships between the plurality of emulatableaspects included in the personalized plan comprises: means fordeveloping the personalized plan by defining in the personalized plan aspecific time relationship or relationships between the plurality ofemulatable aspects included in the personalized plan.
 185. (canceled)186. The computationally-implemented system of claim 97, wherein saidmeans for developing the personalized plan by at least determining whichof the plurality of reported aspects associated with the source user arerelevant to the achievement of the one or more target outcomescomprises: means for developing the personalized plan by including intothe personalized plan at least one plausible emulatable aspect, the atleast one plausible emulatable aspect being at least one emulatableaspect that has been successfully emulated by one or more other endusers.
 187. The computationally-implemented system of claim 186, whereinsaid means for developing the personalized plan by including into thepersonalized plan at least one plausible emulatable aspect, the at leastone plausible emulatable aspect being at least one emulatable aspectthat has been successfully emulated by one or more other end userscomprises: means for developing the personalized plan by including intothe personalized plan at least one plausible emulatable aspect, the atleast one plausible emulatable aspect being at least one emulatableaspect that has been successfully emulated by the one or more other endusers in order to achieve at least one of the one or more targetoutcomes.
 188. The computationally-implemented system of claim 97,further comprising: means for presenting the personalized plan. 189-193.(canceled)
 194. A computer program product comprising: a signal-bearingmedium bearing: (a) one or more instructions for receiving a request fora personalized plan designed to facilitate an end user to achieve one ormore target outcomes when one or more emulatable aspects indicated bythe personalized plan are emulated, the request identifying at least asource user; (b) one or more instructions for acquiring source user dataindicating a plurality of reported aspects associated with at least thesource user in response to receiving the request; and (c) one or moreinstructions for developing the personalized plan by at leastdetermining which of the plurality of reported aspects associated withthe source user are relevant to the achievement of the one or moretarget outcomes.